Glasgow Surname Project

Individual research record

Nancy (Unknown) Glasgow

c. 1785 – c. 1850

Unknown-658277 · 1 mapped association

South CarolinaGiles County, TN, USA

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
6Close relations
3Evidence items
7Candidate leads
Birth
c. 1785 · South Carolina
Death
c. 1850 · Giles County, TN, USA
Parents
Not recorded
Spouses
Robert Glasgow
Children
Emma GlasgowJames J GlasgowJessie M GlasgowJohn GlasgowPriscilla Glasgow
Gender
Female
WikiTree
Unknown-658277
Research clusters
Worldwide One-Tree profile leads
Mapped descendants
23

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 positionJohn Glasgow (1800)
Maternal grandfather positionNot identifiable from dated child profiles
Maternal grandmother positionEmma Glasgow (1815)
Paternal grandmother positionJessie M Glasgow (1818)

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

Automated fit19/100
Weak Lead
Dates1767–1833Generation18 years age gapRecorded placesInishrush, Tamlaght O’Crilly, County Londonderry · St Nossonus — Tamlaght O'Crilly Lower graveyardIndependent clue breadth · 6Age · Contemporaneous Household Conflict · Household · Rare Branch-Name Recurrence · Rare Name Bundle · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 18-year parent-child age gap (+18)
  • candidate's birth is 33 years before the subject's earliest dated child (1800), a marginal two-generation interval (+1)
  • a known child was born within 5 years of the subject (+1)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction); candidate's household recorded Eliza Glasgow in Inishrush, Tamlaght O’Crilly, County Londonderry within 5 years of the subject (−12; no contemporaneous child is indexed in the subject's locality); candidate already has another child named Nancy Glasgow (Glasgow-3907) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Show complete scoring
  • plausible 18-year parent-child age gap (+18)
  • candidate's birth is 33 years before the subject's earliest dated child (1800), a marginal two-generation interval (+1)
  • a known child was born within 5 years of the subject (+1)
  • uncommon given names recur in both otherwise distinct descendant branches: Eliza +8 (23 public profiles; subject branch: Eliza A Glasgow; candidate branch: Eliza Glasgow); Nancy +3 (49 public profiles; subject branch: Nancy (Unknown) Glasgow; candidate branch: Nancy Glasgow) (+15 total including +4 multi-name bonus)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction); candidate's household recorded Eliza Glasgow in Inishrush, Tamlaght O’Crilly, County Londonderry within 5 years of the subject (−12; no contemporaneous child is indexed in the subject's locality); candidate already has another child named Nancy Glasgow (Glasgow-3907) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Automated fit13/100
Weak Lead
Dates1778–1822Generationnominally 7 years; approximate dates permit about 15–17 years age gapRecorded placesKilloquin electoral divisionIndependent clue breadth · 3Age · Rare Branch-Name Recurrence · Rare Name BundleCurrent relationshipNot currently linked as parent
Strongest signals
  • the nominal 7-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (15–17 years) (+4)
  • uncommon given names recur in both otherwise distinct descendant branches: Eliza +10 (23 public profiles; subject branch: Eliza A Glasgow; candidate branch: Eliza Glasgow, Eliza (Glasgow) Haigh; +2 repetition bonus); Nancy +3 (49 public profiles; subject branch: Nancy (Unknown) Glasgow; candidate branch: Nancy Glasgow) (+17 total including +4 multi-name bonus)

parentage requires the approximate birth estimate to be early enough (no deduction); candidate-to-earliest-child interval of 22 years is implausible for two generations (−8); locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • the nominal 7-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (15–17 years) (+4)
  • uncommon given names recur in both otherwise distinct descendant branches: Eliza +10 (23 public profiles; subject branch: Eliza A Glasgow; candidate branch: Eliza Glasgow, Eliza (Glasgow) Haigh; +2 repetition bonus); Nancy +3 (49 public profiles; subject branch: Nancy (Unknown) Glasgow; candidate branch: Nancy Glasgow) (+17 total including +4 multi-name bonus)

Deductions and cautions: parentage requires the approximate birth estimate to be early enough (no deduction); candidate-to-earliest-child interval of 22 years is implausible for two generations (−8); locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show 3 lower-scoring possible mothers
Automated fit22/100
Chronology-Only Fallback
Dates1760–?Generation25 years age gapRecorded placesLocation not supplied — profile holding pointIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 25-year parent-child age gap (+18)
  • candidate's birth is 40 years before the subject's earliest dated child (1800), 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 25-year parent-child age gap (+18)
  • candidate's birth is 40 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

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

Automated fit22/100
Chronology-Only Fallback
Dates1750–?Generation35 years age gapRecorded placesCounty Antrim — exact locality unprovedIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 35-year parent-child age gap (+18)
  • candidate's birth is 50 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)

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

Show complete scoring
  • plausible 35-year parent-child age gap (+18)
  • candidate's birth is 50 years before the subject's earliest dated child (1800), a compatible grandparent-generation interval (+4)

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

Automated fit19/100
Chronology-Only Fallback
Dates1767–1812Generation18 years age gapRecorded placesNottingham, West Nottingham Township, Chester, PennsylvaniaIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 18-year parent-child age gap (+18)
  • candidate's birth is 33 years before the subject's earliest dated child (1800), a marginal two-generation interval (+1)
  • 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 18-year parent-child age gap (+18)
  • candidate's birth is 33 years before the subject's earliest dated child (1800), a marginal two-generation interval (+1)
  • same research cluster (+0; grouping is not kinship evidence)

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 fit36/100
Similar Person
Dates1788–1868PlacesVirginia, United States → Virginia, United StatesParent 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

Automated fit28/100
Similar Person
Dates1843–1849PlacesOhio, United States → Tranquility, Scott Township, Adams, Ohio, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • death years within 1 (+10)

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

Full comparison detail
  • same first and last name (+18)
  • death years within 1 (+10)

Conflicts: record-derived birth estimates differ by 58; 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

Latest case researchThe current conclusion from the durable research case file.Updated

Current conclusion

Unknown-658277 · updated 2026-08-12

Nancy's first name, maiden name and vital dates have not been proved by a contemporary record. A female aged 50–59 was present in Robert Glasgow-2769's 1840 household and could be his wife, but the census states no name or relationship. Her absence from Robert's 1850 household does not by itself prove that she died in 1850.

The 19 January 1814 Delaware marriage of Robert Glasgow and Nancy Black is a different family. A Robert Glasgow also appears in Delaware militia records, and FamilySearch's sourced reconstruction gives the Delaware couple a son born there about 1825. Meanwhile the target Robert served in Tennessee and remained in the Giles County census in 1820. The surname Black must not be assigned to this profile.

Life and record timelineChronological mapped occurrences and their underlying sources.1 record
b. 1785

Profile-stated birthplace: South Carolina

South Carolina

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-658277

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.7 claims
2Tree Only
1Unknown

Documented or strongly supported

No claims in this category have been formally assessed.

Working hypotheses and conflicts

Nancy (Unknown) Glasgow was wife of Robert Glasgow

possible1 linked evidence item

Robert's 1840 household contains a female aged 50–59, but no source names her. The 1814 Delaware bride Nancy Black belonged to a different couple.

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-658277 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2023-10-27.

Profile location claims

EventDateLocationStatus
birthSouth CarolinaWikiTree profile field
deathGiles County, TN, USAWikiTree profile field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ChildrenJohn GlasgowGlasgow-27701800-00-00 · South Carolina, United States · 0000-00-00
ChildrenJames J GlasgowGlasgow-27381810-00-00 · South Carolina, United States · 0000-00-00
ChildrenEmma GlasgowGlasgow-27711815-00-00 · South Carolina, United States · 0000-00-00
ChildrenJessie M GlasgowGlasgow-27721818-00-00 · Giles, Tennessee, United States · 1886-00-00 · Upshur, Texas, United States
ChildrenPriscilla GlasgowGlasgow-27731822-00-00 · Tennessee, United States · 0000-00-00
SpousesRobert GlasgowGlasgow-27691780-00-00 · South Carolina, USA · 1860-00-00 · Giles County, TN, USA · 1799-00-00

Record-bearing passages

  • Biography Nancy was born about 1785. She passed away about 1850. Sources

    • FTDNA tree of YDNA relative

Profile source citations

  1. FTDNA tree of YDNA relative
Full captured biography text
Biography
Nancy was born about 1785. She passed away about 1850.
Sources
* FTDNA tree of YDNA relative
Raw WikiTree biography markup
== Biography ==

Nancy was born about 1785.  She passed away about 1850.
== Sources ==
<references />
* FTDNA tree of YDNA relative