Glasgow Surname Project

Individual research record

Annie (Unknown) Glasco

c. 1878 – ?

Unknown-522347 · 1 mapped association

Pennsylvania, United StatesDeath place unknown

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
5Close relations
1Evidence items
7Candidate leads
Birth
c. 1878 · Pennsylvania, United States
Death
Not recorded · Place not recorded
Parents
Not recorded
Spouses
Richard B Glasgow
Children
Eliza GlascoGeorge GlascoHenry GlascoLiving person (details withheld)
Gender
Female
WikiTree
Unknown-522347
Research clusters
Worldwide 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 positionHenry Glasco (1900)
Maternal grandfather positionGeorge Glasco (1904)
Maternal grandmother positionEliza Glasco (1898)
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 mothers5 leads

Automated fit15/100
Weak Lead
Dates1854–?Generation24 years age gapRecorded placesCounty Londonderry, Ireland · County Londonderry — exact locality unprovedIndependent clue breadth · 6Age · Household · Rare Branch-Name Recurrence · Sex-Aware Ordered Naming · Tradition Validation · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 24-year parent-child age gap (+18)
  • candidate's birth is 44 years before the subject's earliest dated child (1898), a compatible grandparent-generation interval (+4)
  • a known child was born within 1 years of the subject (+3)

candidate is recorded only outside the subject's birth country (−25)

Show complete scoring
  • plausible 24-year parent-child age gap (+18)
  • candidate's birth is 44 years before the subject's earliest dated child (1898), a compatible grandparent-generation interval (+4)
  • a known child was born within 1 years of the subject (+3)
  • candidate's name matches the first dated daughter Eliza Glasco, the expected mother position for a female subject (+7; catalogue rarity 3, Eliza in 23 profiles)
  • family naming controls: 0 supporting and 1 conflicting known positions (already reflected in naming weight)
  • uncommon given names recur in both otherwise distinct descendant branches: Henry +8 (24 public profiles; subject branch: Henry Glasco; candidate branch: Henry Glasgow) (+8 total)

Deductions and cautions: candidate is recorded only outside the subject's birth country (−25)

Automated fit23/100
Chronology-Only Fallback
Dates1850–1880Generation28 years age gapRecorded placesPennsylvania, United States · Rhode Island, United StatesIndependent clue breadth · 3Age · Broad Geography · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 28-year parent-child age gap (+18)
  • candidate's birth is 48 years before the subject's earliest dated child (1898), 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 28-year parent-child age gap (+18)
  • candidate's birth is 48 years before the subject's earliest dated child (1898), 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 fit12/100
Chronology-Only Fallback
Dates1843–1899Generation35 years age gapRecorded placesDenver, City and County of Denver, Colorado, USAIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 35-year parent-child age gap (+18)
  • candidate's birth is 55 years before the subject's earliest dated child (1898), 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 35-year parent-child age gap (+18)
  • candidate's birth is 55 years before the subject's earliest dated child (1898), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

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

Automated fit0/100
Chronology-Only Fallback
Dates1834–?Generation44 years age gapRecorded placesCounty Tyrone, Ireland · County Tyrone — exact locality unprovedIndependent clue breadth · 3Age · Spouse-Specific Child Window · Two-GenerationSame-spouse child windowJames GlasgowCurrent relationshipNot currently linked as parent
Strongest signals
  • possible 44-year parent-child age gap (+10)
  • candidate's birth is 64 years before the subject's earliest dated child (1898), a compatible grandparent-generation interval (+4)
  • subject's birth fits between children attributed to the same parental couple (1875–1880) (+6; other parent James Glasgow)

candidate is recorded only outside the subject's birth country (−25)

Show complete scoring
  • possible 44-year parent-child age gap (+10)
  • candidate's birth is 64 years before the subject's earliest dated child (1898), a compatible grandparent-generation interval (+4)
  • subject's birth fits between children attributed to the same parental couple (1875–1880) (+6; other parent James Glasgow)

Deductions and cautions: candidate is recorded only outside the subject's birth country (−25)

Automated fit0/100
Chronology-Only Fallback
Dates1825–?Generation53 years age gapRecorded placesGeorgia, United StatesIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • candidate's birth is 73 years before the subject's earliest dated child (1898), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

chronologically conflicting 53-year parent-child age gap (−8); same country, but no indexed locality overlap (−10)

Show complete scoring
  • candidate's birth is 73 years before the subject's earliest dated child (1898), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

Deductions and cautions: chronologically conflicting 53-year parent-child age gap (−8); 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 fit58/100
Similar Person
Dates1878–1971PlacesChester Township, Delaware County, Pennsylvania, United States → Chester Township, Delaware County, Pennsylvania, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • same birth year (+30)
  • overlapping locality (+8)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • same birth year (+30)
  • overlapping locality (+8)
  • child given-name pattern overlaps: Henry

Conflicts: No indexed conflict

Automated fit48/100
Similar Person
Dates1878–?PlacesArkansas, United StatesParent 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

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. 1878

Profile-stated birthplace: Pennsylvania, United States

Pennsylvania, 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-522347

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.5 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 Unknown-522347
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