Glasgow Surname Project

Individual research record

Sarah (Unknown) Glasgow

1789 – 1850

Unknown-729355 · 1 mapped association

IrelandWest Deer Township, Allegheny, Pennsylvania, United States

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
4Close relations
2Evidence items
7Candidate leads
Birth
1789 · Ireland
Death
1850 · West Deer Township, Allegheny, Pennsylvania, United States
Parents
Not recorded
Spouses
Alexander Glasgow
Children
Archibald GlasgowHugh GlasgowRobert S. Glasgow
Gender
Female
WikiTree
Unknown-729355
Research clusters
Ireland One-Tree profile leads
Mapped descendants
5

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 positionHugh Glasgow (1817)
Maternal grandfather positionArchibald Glasgow (1825)
Maternal grandmother positionNot identifiable from dated child profiles
Paternal grandmother positionNot identifiable from dated child profiles

Known-position checks: 1 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 mothers5 leads

Automated fit23/100
Chronology-Only Fallback
Dates1767–1812Generation22 years age gapRecorded placesNottingham, West Nottingham Township, Chester, PennsylvaniaIndependent clue breadth · 3Age · Broad Geography · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 22-year parent-child age gap (+18)
  • candidate's birth is 50 years before the subject's earliest dated child (1817), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: pennsylvania, township, west (+1; not a locality match)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 22-year parent-child age gap (+18)
  • candidate's birth is 50 years before the subject's earliest dated child (1817), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: pennsylvania, township, west (+1; not a locality match)

Deductions and cautions: No indexed conflict; documentary proof still required

Automated fit23/100
Chronology-Only Fallback
Dates1750–?Generation39 years age gapRecorded placesCounty Antrim — exact locality unprovedIndependent clue breadth · 3Age · Broad Geography · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 39-year parent-child age gap (+18)
  • candidate's birth is 67 years before the subject's earliest dated child (1817), a compatible grandparent-generation interval (+4)
  • same broad administrative area only (+1; not a locality match)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 39-year parent-child age gap (+18)
  • candidate's birth is 67 years before the subject's earliest dated child (1817), a compatible grandparent-generation interval (+4)
  • same broad administrative area only (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)

Deductions and cautions: No indexed conflict; documentary proof still required

Show 3 lower-scoring possible mothers
Automated fit22/100
Chronology-Only Fallback
Dates1760–?Generation29 years age gapRecorded placesLocation not supplied — profile holding pointIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 29-year parent-child age gap (+18)
  • candidate's birth is 57 years before the subject's earliest dated child (1817), 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 29-year parent-child age gap (+18)
  • candidate's birth is 57 years before the subject's earliest dated child (1817), 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 fit15/100
Chronology-Only Fallback
Dates1767–1833Generation22 years age gapRecorded placesInishrush, Tamlaght O’Crilly, County Londonderry · St Nossonus — Tamlaght O'Crilly Lower graveyardIndependent clue breadth · 3Age · Household · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 22-year parent-child age gap (+18)
  • candidate's birth is 50 years before the subject's earliest dated child (1817), a compatible grandparent-generation interval (+4)
  • a known child was born within 1 years of the subject (+3)

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

Show complete scoring
  • plausible 22-year parent-child age gap (+18)
  • candidate's birth is 50 years before the subject's earliest dated child (1817), a compatible grandparent-generation interval (+4)
  • a known child was born within 1 years of the subject (+3)

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

Automated fit0/100
Chronology-Only Fallback
Dates1783–?Generationnominally 6 years; approximate dates permit about 15–16 years age gapRecorded placesCounty Tyrone — exact locality unprovedIndependent clue breadth · 3Age · Broad Migration · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • the nominal 6-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (15–16 years) (+4)
  • candidate's birth is 34 years before the subject's earliest dated child (1817), a marginal two-generation interval (+1)
  • same research cluster (+0; grouping is not kinship evidence)

parentage requires the approximate birth estimate to be early enough (no deduction); same country, but no indexed locality overlap (−10)

Show complete scoring
  • the nominal 6-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (15–16 years) (+4)
  • candidate's birth is 34 years before the subject's earliest dated child (1817), a marginal two-generation interval (+1)
  • same research cluster (+0; grouping is not kinship evidence)
  • descendant branches share only a broad migration destination country (+1; weak alone): united states

Deductions and cautions: parentage requires the approximate birth estimate to be early enough (no deduction); 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 fit54/100
Similar Person
Dates1757–1840PlacesIreland → Allegheny, Pennsylvania, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • shared recorded place (+20)
  • matching child name: Hugh Glasgow

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

Full comparison detail
  • same first and last name (+18)
  • shared recorded place (+20)
  • matching child name: Hugh Glasgow
  • child given-name pattern overlaps: Robert

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

Automated fit43/100
Similar Person
Dates1790–?PlacesWythe County Virginia → Pulaski County VirginiaParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 1 (+25)

No indexed conflict

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

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
Evidence assessmentWhat is supported, uncertain or disputed in the current case model.5 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 US Census & others to be added asap
  2. tree_only WikiTree profile export for Unknown-729355
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-729355 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2025-08-06.

Profile location claims

EventDateLocationStatus
birthIrelandWikiTree profile field
deathWest Deer Township, Allegheny, Pennsylvania, United StatesWikiTree profile field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ChildrenHugh GlasgowGlasgow-36361817-00-00 · West Deer Township, Allegheny, Pennsylvania, United States · 1874-00-00
ChildrenArchibald GlasgowGlasgow-36371825-00-00 · West Deer Township, Allegheny, Pennsylvania, United States · 0000-00-00
ChildrenRobert S. GlasgowGlasgow-9951827-05-00 · West Deer Township, Allegheny, Pennsylvania, United States · 1901-01-01 · Alleghehy, Pennsylvania, United States
SpousesAlexander GlasgowGlasgow-5441786-02-26 · Ireland · 1855-12-04 · Allegheny, Pennsylvania, United States · 0000-00-00

Record-bearing passages

  • Biography Sarah was born in 1789. She passed away in 1850. Sources

    • US Census & others to be added asap

Profile source citations

  1. US Census & others to be added asap
Full captured biography text
Biography
Sarah was born in 1789. She passed away in 1850.
Sources
* US Census & others to be added asap
Raw WikiTree biography markup
== Biography ==

Sarah was born in 1789.  She passed away in 1850.
== Sources ==
<references />
* US Census & others to be added asap