Glasgow Surname Project

Individual research record

Mary (Unknown) Glasgow

1813 – ?

Unknown-653364 · 1 mapped association

Tennessee, United StatesDeath place unknown

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
1Close relations
3Evidence items
13Candidate leads
Birth
1813 · Tennessee, United States
Death
Not recorded · Place not recorded
Parents
Not recorded
Spouses
James J Glasgow
Children
Not recorded
Gender
Female
WikiTree
Unknown-653364
Research clusters
Worldwide One-Tree profile leads
Mapped descendants
0

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 positionNot identifiable from dated child profiles
Maternal grandfather positionNot identifiable from dated child profiles
Maternal grandmother positionNot identifiable from dated child profiles
Paternal grandmother positionNot identifiable from dated child profiles

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

Estimate and relationship notes
  • WikiTree marks this person as having children, but no named child profile is recoverable from this export.

Relationship comparison

Potential parents or duplicates

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

Higher-signal leadReview carefullyWeak lead

No named children are recoverable, so child-naming analysis cannot be run.

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 fit43/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)

No indexed conflict

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

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 fit40/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)

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

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

Same-name candidate

Mary GlasgowGlasgow-2971

Automated fit36/100
Similar Person
Dates1816–?PlacesPlaces not recordedParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 3 (+18)

No indexed conflict

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

Conflicts: No indexed conflict

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 Unknown-653364

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.2 claims
2Derivative
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.3 sources
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

Unknown-653364 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2023-09-02.

Profile location claims

EventDateLocationStatus
birthTennessee, United StatesWikiTree profile field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ChildrenFleming N GlasgowGlasgow-27391839-00-00 · Alabama, United States · 0000-00-00
ChildrenEliza A GlasgowGlasgow-27401843-00-00 · Tennessee, United States · 0000-00-00
ChildrenJames GlasgowGlasgow-27411845-00-00 · Tennessee, United States · 0000-00-00
ChildrenThomas Taylor GlasgowGlasgow-27421848-00-00 · Tennessee, United States · 0000-00-00
ChildrenEmma C BarnettGlasgow-27431852-00-00 · Tennessee, United States · 0000-00-00
ChildrenJoseph P GlasgowGlasgow-27441854-00-00 · Tennessee, United States · 0000-00-00
ChildrenEdward Buchanan GlasgowGlasgow-27361856-00-00 · Giles, Tennessee, United States · 1883-08-02 · Pulaski, Giles, Tennessee, United States
SpousesJames J GlasgowGlasgow-27381810-00-00 · South Carolina, United States · 0000-00-00

Record-bearing passages

Profile source citations

  1. "United States Census, 1860", database with images, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:M6GF-RXZ : Tue Jul 18 02:43:56 UTC 2023), Entry for Jas J Glasgow and Mary J Glasgow, 1860. source link 1
  2. "United States Census, 1870", database with images, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:MD8B-K5W : Mon Aug 21 22:25:37 UTC 2023), Entry for Mary Glascow and James R Glascow, 1870. source link 1
Full captured biography text
BiographyResearch Notes
Some public trees suggest that her full name was Mary Caroline Thompson.
Sources
* "United States Census, 1860", database with images, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:M6GF-RXZ : Tue Jul 18 02:43:56 UTC 2023), Entry for Jas J Glasgow and Mary J Glasgow, 1860.
* "United States Census, 1870", database with images, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:MD8B-K5W : Mon Aug 21 22:25:37 UTC 2023), Entry for Mary Glascow and James R Glascow, 1870.
Raw WikiTree biography markup
== Biography ==

== Research Notes ==
Some public trees suggest that her full name was Mary Caroline Thompson.
== Sources ==
<references />
* "United States Census, 1860", database with images, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:M6GF-RXZ : Tue Jul 18 02:43:56 UTC 2023), Entry for Jas J Glasgow and Mary J Glasgow, 1860.
* "United States Census, 1870", database with images, FamilySearch (https://www.familysearch.org/ark:/61903/1:1:MD8B-K5W : Mon Aug 21 22:25:37 UTC 2023), Entry for Mary Glascow and James R Glascow, 1870.