Glasgow Surname Project

Individual research record

Mary Caroline (Thompson) Glasgow

1813 – ?

Thompson-109946 · 1 mapped association

Tennessee, United StatesDeath place unknown

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
8Close relations
1Evidence items
9Candidate leads
Birth
1813 · Tennessee, United States
Death
Not recorded · Place not recorded
Parents
Not recorded
Spouses
James J Glasgow
Children
Edward Buchanan GlasgowEliza A GlasgowEmma C (Glasgow) BarnettFleming N GlasgowJames K P GlasgowJoseph P GlasgowThomas Taylor Glasgow
Gender
Female
WikiTree
Thompson-109946
Research clusters
Worldwide One-Tree profile leads
Mapped descendants
18

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 positionFleming N Glasgow (1839)
Maternal grandfather positionJames K P Glasgow (1845)
Maternal grandmother positionEliza A Glasgow (1843)
Paternal grandmother positionEmma C (Glasgow) Barnett (1852)

Known-position checks: 0 support · 0 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 mothers1 leads

Automated fit16/100
Weak Lead
Dates1795–?Generation18 years age gapRecorded placesNicholas, Kentucky, United StatesIndependent clue breadth · 3Age · Same-Sex Generational Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 18-year parent-child age gap (+18)
  • candidate's birth is 44 years before the subject's earliest dated child (1839), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

same country, but no indexed locality overlap (−10)

Show complete scoring
  • plausible 18-year parent-child age gap (+18)
  • candidate's birth is 44 years before the subject's earliest dated child (1839), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name Mary (+4; weak direct parent-child name recurrence, 254 public profiles)

Deductions and cautions: same country, but no indexed locality overlap (−10)

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 fit98/100
Possible Duplicate
Dates1813–?PlacesTennessee, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • same birth year (+30)
  • shared recorded place (+20)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • same birth year (+30)
  • shared recorded place (+20)
  • same spouse profile (+30)

Conflicts: No indexed conflict

Automated fit48/100
Similar Person
Dates1820–?PlacesPlaces not recordedParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 7 (+10)
  • shared recorded place (+20)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 7 (+10)
  • shared recorded place (+20)

Conflicts: No indexed conflict

Automated fit45/100
Similar Person
Dates1811–?PlacesPlaces not recordedParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 2 (+25)
  • child given-name pattern overlaps: James

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 2 (+25)
  • child given-name pattern overlaps: James

Conflicts: No indexed conflict

Same-name candidate

Mary GlasgowGlasgow-2902

Automated fit43/100
Similar Person
Dates1815–1850PlacesPlaces not recordedParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 2 (+25)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 2 (+25)

Conflicts: No indexed conflict

Show 4 lower-scoring duplicate lead(s)
Automated fit42/100
Similar Person
Dates1826–?PlacesTennessee, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 13 (+2)
  • shared recorded place (+20)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 13 (+2)
  • shared recorded place (+20)
  • child given-name pattern overlaps: James

Conflicts: No indexed conflict

Automated fit40/100
Similar Person
Dates1832–1865PlacesTennessee, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 19 (+2)
  • shared recorded place (+20)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 19 (+2)
  • shared recorded place (+20)

Conflicts: No indexed conflict

Automated fit38/100
Similar Person
Dates1817–1866PlacesLisnagaver, County Antrim, IrelandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 4 (+18)
  • child given-name pattern overlaps: James

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 4 (+18)
  • child given-name pattern overlaps: James

Conflicts: No indexed conflict

Same-name candidate

Mary GlasgowGlasgow-2481

Automated fit38/100
Similar Person
Dates1861–?PlacesTennessee, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • shared recorded place (+20)

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

Full comparison detail
  • same first and last name (+18)
  • shared recorded place (+20)

Conflicts: record-derived birth estimates differ by 48; 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
b. 1813

Profile-stated birthplace: Tennessee, United States

Tennessee, United States

One-Tree export profile fields are search leads, not sources; relationships are shown only where the export supplies parent links.

One-Tree profile leadunknown
Source and mapping detail

WikiTree profile export for Thompson-109946

No sufficiently specific citation match found.

Precision: Country-centre fallback for profile locality

Evidence assessmentWhat is supported, uncertain or disputed in the current case model.9 claims
1Tree Only

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.1 source

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

  1. tree_only WikiTree profile export for Thompson-109946
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