Glasgow Surname Project

Individual research record

Elizabeth (Campbell) Glasgow

1830 – ?

Campbell-72380 · 1 mapped association

Birthplace unknownDeath place unknown

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
5Close relations
2Evidence items
4Candidate leads
Birth
1830 · Place not recorded
Death
Not recorded · Place not recorded
Parents
Not recorded
Spouses
Robert Glasgow
Children
Alexander GlasgowArchibald GlasgowRobert GlasgowWilliam Glasgow
Gender
Female
WikiTree
Campbell-72380
Research clusters
Scotland One-Tree profile leads
Mapped descendants
4

Comparison context

These child positions and checks are the subject details used to rank possible parents below.

Naming sequence used by the parentage model

Paternal grandfather positionRobert Glasgow (1868)
Maternal grandfather positionArchibald Glasgow (1870)
Maternal grandmother positionNot identifiable from dated child profiles
Paternal grandmother positionNot identifiable from dated child profiles

Known-position checks: 0 support · 1 conflict. Ordinals retain unnamed children and recognise reused names.

Relationship comparison

Potential parents or duplicates

Compare scored leads with the subject details above—not proof.

Higher-signal leadReview carefullyWeak lead

Possible mothers2 leads

Automated fit32/100
Weak Lead
Dates1797–1852Generation33 years age gapRecorded placesPatrick, Lanarkshire, Scotland · Glasgow, Lanarkshire, Scotland, United Kingdom · Lanarkshire — exact locality unprovedIndependent clue breadth · 4Age · Same-Sex Generational Naming · Spouse-Specific Child Window · Two-GenerationSame-spouse child windowJohn GlasgowCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 33-year parent-child age gap (+18)
  • candidate's birth is 71 years before the subject's earliest dated child (1868), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 33-year parent-child age gap (+18)
  • candidate's birth is 71 years before the subject's earliest dated child (1868), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • subject's birth fits between children attributed to the same parental couple (1818–1836) (+6; other parent John Glasgow)
  • candidate and subject share the given name Elizabeth (+4; weak direct parent-child name recurrence, 146 public profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Automated fit15/100
Chronology-Only Fallback
Dates1788–1877Generation42 years age gapRecorded placesRockbridge, Virginia, United States · Adams, Ohio, United StatesIndependent clue breadth · 3Age · Household · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • possible 42-year parent-child age gap (+10)
  • candidate's birth is 80 years before the subject's earliest dated child (1868), a compatible grandparent-generation interval (+4)
  • a known child was born within 4 years of the subject (+1)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • possible 42-year parent-child age gap (+10)
  • candidate's birth is 80 years before the subject's earliest dated child (1868), a compatible grandparent-generation interval (+4)
  • a known child was born within 4 years of the subject (+1)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

How parent leads are calculated

Automated leads use birth surnames—not married surnames—as parental eligibility, role-specific biological age limits, bounded and approximate-date uncertainty, household chronology, specific time-aware localities, mapped distance, tenancy succession, migration destinations and sex-aware Scottish naming positions across generations. People already attached as the subject's parents stay in the identity summary and are excluded from this alternative-candidate list, regardless of relationship confidence. The main calibration uses clues available on disconnected profiles; existing parent and sibling links are retained as comparison context rather than treated as transferable evidence. Common ordered names and grandparent-to-child echoes receive a small non-zero weight, so a John or James match can support several independent criteria without producing a lead alone. Rare names, repeated bearers and bundles across otherwise distinct branches receive substantially more weight according to catalogue frequency. An exact migration place is weighted by its rarity and repetition across both branches; a shared destination country is worth only one point. Extra weight is added only when at least three independent clue types converge: naming, locality, specific migration, household chronology or collateral networks. Sparse profiles retain a clearly labelled chronology-only fallback instead of disappearing. Countries, states, counties and research clusters do not count as a shared locality, and fallback, broad representative or kin-inferred coordinates are excluded from distance scoring. Shared descendant profiles are removed before branch-name comparison. A candidate already recorded as a parent-in-law is excluded. A confident or independently supported parent is treated as settled; uncertain and unassessed attachments remain open to alternative comparison. A different linked parent, an uncle/aunt or grandparent path, and a matching existing child profile prevent an alternative from being classified as a strong direct-parent lead until the underlying tree conflict or duplicate is resolved. Familiar forms such as Bessie are normalised. Surname remains an eligibility filter worth zero points.

Naming customs, shared farms and occupations are circumstantial. Children, spouses and collateral relatives may be missing, and tree-derived family networks are not independent evidence. Scores rank research leads; they do not prove parentage.

Automated fit48/100
Similar Person
Dates1830–1909PlacesPlaces not recordedParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • same birth year (+30)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • same birth year (+30)

Conflicts: No indexed conflict

Automated fit40/100
Similar Person
Dates1795–1885PlacesSouth Carolina, United States → Warrior, Jefferson, Alabama, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • same spouse name (+20)
  • child given-name pattern overlaps: Robert

record-derived birth estimates differ by 35; retained without deduction

Full comparison detail
  • same first and last name (+18)
  • same spouse name (+20)
  • child given-name pattern overlaps: Robert

Conflicts: record-derived birth estimates differ by 35; retained without deduction

How duplicate leads are calculated

Dates are eligibility gates, not merely deductions: chronologically impossible people are excluded. Dates, places, spouses, parent certainty and children's profiles and names are then compared. A high score is a prompt to inspect records, not a merge recommendation.

Open only what you need

Research & records

Life and record timelineChronological mapped occurrences and their underlying sources.1 record
Evidence assessmentWhat is supported, uncertain or disputed in the current case model.6 claims
1Tree Only
1Unknown

Documented or strongly supported

No claims in this category have been formally assessed.

Working hypotheses and conflicts

No claims in this category have been formally assessed.

Research questionsOpen problems, missing bridges and the next records to inspect.0 open

No formal open question is recorded for this person.

Sources and provenanceStructured citations and source-quality classifications.2 sources

Source or provenance: quality describes the record layer, not every conclusion drawn from it.

  1. unknown see husband
  2. tree_only WikiTree profile export for Campbell-72380
Technical profile and raw captureDataset metadata, machine dossier and captured WikiTree biography.Advanced

WikiTree profile information

Dataset: ONT_Glasco_2026-08-18T16_05.json · generated 2026-08-20

Machine-readable dossier

WikiTree biography, citations and relationship snapshot

Campbell-72380 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2025-03-27.

Profile location claims

EventDateLocationStatus
marriage1867-04-11Bathgate, West Lothian, ScotlandWikiTree relationship field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ChildrenRobert GlasgowGlasgow-15951868-00-00 · Armadale, Linlithgowshire, Scotland, United Kingdom · 0000-00-00
ChildrenArchibald GlasgowGlasgow-33061870-02-02 · Bathgate, Linlithgowshire, Scotland, United Kingdom · 1871-03-12 · Armadale, Linlithgowshire, Scotland, United Kingdom
ChildrenAlexander GlasgowGlasgow-15961871-11-14 · Bathgate,West Lothian,Scotland · 1941-12-04 · Armadale, West Lothian, Scotland, United Kingdom
ChildrenWilliam GlasgowGlasgow-15971875-00-00 · Coytton, Ayrshire, Scotland, United Kingdom · 0000-00-00
SpousesRobert GlasgowGlasgow-15941829-00-00 · Lanarkshire · 0000-00-00 · 1867-04-11 · Bathgate, West Lothian, Scotland

Record-bearing passages

  • Biography Elizabeth was born in 1830. Sources

    • see husband

Profile source citations

  1. see husband
Full captured biography text
Biography
Elizabeth was born in 1830.
Sources
* see husband
Raw WikiTree biography markup
== Biography ==
Elizabeth was born in 1830.
== Sources ==
<references />
* see husband