Glasgow Surname Project

Individual research record

Benjamin Douglas Thomas Glasco

1860-05-07 – 1944-09-29

Glasco-38 · 1 mapped association

Morgan County, Indiana, United States→Athens, Gentry, Missouri, United States
View on mapOpen WikiTreeCompareReport a correction

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
2Close relations
1Evidence items
12Candidate leads
Birth
1860-05-07 · Morgan County, Indiana, United States
Death
1944-09-29 · Athens, Gentry, Missouri, United States
Parents
Not recorded
Spouses
Virginia Lenora (Steele) Glasco
Children
Lola Glasco
Gender
Male
WikiTree
Glasco-38
Research clusters
Worldwide One-Tree profile leads
Mapped descendants
1

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 positionLola Glasco (1886)
Paternal grandmother positionNot identifiable from dated child profiles

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 fathers5 leads

Automated fit21/100
Weak Lead
Dates1827–1897Generation33 years age gapRecorded placesBlair, Pennsylvania, United States · Calvin, Union Township, Huntingdon, Pennsylvania, United StatesIndependent clue breadth · 6Age · Contemporaneous Household Conflict · Same-Sex Generational Naming · Spouse · Spouse-Specific Child Window · Two-GenerationSame-spouse child windowMatilda (Myerly) GlasgowCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 33-year parent-child age gap (+18)
  • known spouse Matilda (Myerly) Glasgow had a plausible maternal age (24) at the subject's birth (+7)
  • candidate's birth is 59 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)

same country, but no indexed locality overlap (−10); candidate's household recorded Prudence J (Glasgow) Wright in Union Township, Huntingdon, Pennsylvania, United States within 1 years of the subject (−12; no contemporaneous child is indexed in the subject's locality)

Show complete scoring
  • plausible 33-year parent-child age gap (+18)
  • candidate's birth is 59 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • subject's birth fits between children attributed to the same parental couple (1859–1866) (+6; other parent Matilda (Myerly) Glasgow)
  • known spouse Matilda (Myerly) Glasgow had a plausible maternal age (24) at the subject's birth (+7)
  • candidate and subject share the given name Benjamin (+8; weak direct parent-child name recurrence, 13 public profiles)

Deductions and cautions: same country, but no indexed locality overlap (−10); candidate's household recorded Prudence J (Glasgow) Wright in Union Township, Huntingdon, Pennsylvania, United States within 1 years of the subject (−12; no contemporaneous child is indexed in the subject's locality)

Automated fit20/100
Weak Lead
Dates1827–?Generation33 years age gapRecorded placesVirginia, United StatesIndependent clue breadth · 3Age · Same-Sex Generational Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 33-year parent-child age gap (+18)
  • candidate's birth is 59 years before the subject's earliest dated child (1886), 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 33-year parent-child age gap (+18)
  • candidate's birth is 59 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name Benjamin (+8; weak direct parent-child name recurrence, 13 public profiles)

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

Show 3 lower-scoring possible fathers
Automated fit12/100
Weak Lead
Dates1843–1925Generation17 years age gapRecorded placesPennsylvania, United States · Philadelphia, Pennsylvania, United StatesIndependent clue breadth · 3Age · Same-Sex Generational Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • possible 17-year parent-child age gap (+10)
  • candidate's birth is 43 years before the subject's earliest dated child (1886), 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
  • possible 17-year parent-child age gap (+10)
  • candidate's birth is 43 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name Benjamin (+8; weak direct parent-child name recurrence, 13 public profiles)

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

Automated fit12/100
Weak Lead
Dates1841–1916Generation19 years age gapRecorded placesIreland, United Kingdom · Belle Center, Logan County, Ohio, United States · Ireland — exact locality unprovedIndependent clue breadth · 3Age · Same-Sex Generational Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • possible 19-year parent-child age gap (+10)
  • candidate's birth is 45 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • candidate and subject share the given name Benjamin (+8; weak direct parent-child name recurrence, 13 public profiles)

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

Show complete scoring
  • possible 19-year parent-child age gap (+10)
  • candidate's birth is 45 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • candidate and subject share the given name Benjamin (+8; weak direct parent-child name recurrence, 13 public profiles)

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

Automated fit8/100
Weak Lead
Dates1840–1901Generation20 years age gapRecorded placesIreland, United Kingdom · Ireland — exact locality unprovedIndependent clue breadth · 4Age · Same-Sex Generational Naming · Spouse · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 20-year parent-child age gap (+18)
  • candidate's birth is 46 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • known spouse Adelaide Glasgow had a bounded, possibly plausible maternal age (23) at the subject's birth (+3)

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

Show complete scoring
  • plausible 20-year parent-child age gap (+18)
  • candidate's birth is 46 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • known spouse Adelaide Glasgow had a bounded, possibly plausible maternal age (23) at the subject's birth (+3)
  • candidate and subject share the given name Benjamin (+8; weak direct parent-child name recurrence, 13 public profiles)

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

Possible mothers5 leads

Automated fit24/100
Weak Lead
Dates1831–?Generation29 years age gapRecorded placesOhioIndependent clue breadth · 5Age · Contemporaneous Household Conflict · Rare Branch-Name Recurrence · Spouse-Specific Child Window · Two-GenerationSame-spouse child windowThomas GlascoCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 29-year parent-child age gap (+18)
  • candidate's birth is 55 years before the subject's earliest dated child (1886), 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); candidate's household recorded George Glasco in District Of Columbia within 3 years of the subject (−12; no contemporaneous child is indexed in the subject's locality); candidate already has another child named Benjamin Glasco (Glasco-16) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Show complete scoring
  • plausible 29-year parent-child age gap (+18)
  • candidate's birth is 55 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • subject's birth fits between children attributed to the same parental couple (1857–1872) (+6; other parent Thomas Glasco)
  • uncommon given names recur in both otherwise distinct descendant branches: Benjamin +12 (13 public profiles; subject branch: Benjamin Douglas Thomas Glasco; candidate branch: Benjamin Glasco) (+12 total)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction); candidate's household recorded George Glasco in District Of Columbia within 3 years of the subject (−12; no contemporaneous child is indexed in the subject's locality); candidate already has another child named Benjamin Glasco (Glasco-16) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Automated fit0/100
Weak Lead
Dates1853–1901Generationnominally 7 years; approximate dates permit about 15–17 years age gapRecorded placesDrumshanbo, Kildress, Cookstown, County Tyrone, Ireland · Gortin, Derryloran, Cookstown, County Tyrone, Ireland · Kildress civil parishIndependent clue breadth · 3Age · Repeated Marriage Surnames · Two-GenerationCurrent 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)
  • candidate's birth is 33 years before the subject's earliest dated child (1886), a marginal two-generation interval (+1)
  • uncommon spouse surnames recur across the subject and candidate branches: Steele +8 (+8 total)

parentage requires the approximate birth estimate to be early enough (no deduction); candidate is recorded only outside the subject's birth country (−25)

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)
  • candidate's birth is 33 years before the subject's earliest dated child (1886), a marginal two-generation interval (+1)
  • uncommon spouse surnames recur across the subject and candidate branches: Steele +8 (+8 total)

Deductions and cautions: parentage requires the approximate birth estimate to be early enough (no deduction); candidate is recorded only outside the subject's birth country (−25)

Show 3 lower-scoring possible mothers
Automated fit0/100
Weak Lead
Dates1800–1879Generation60 years age gapRecorded placesVirginia, United StatesIndependent clue breadth · 3Age · Rare Branch-Name Recurrence · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • candidate's birth is 86 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • uncommon given names recur in both otherwise distinct descendant branches: Benjamin +12 (13 public profiles; subject branch: Benjamin Douglas Thomas Glasco; candidate branch: Benjamin M. Glasgow) (+12 total)

chronologically conflicting 60-year parent-child age gap (−8); same country, but no indexed locality overlap (−10); subject lies more than 20 years from the candidate's known child-bearing period (−6; children may be missing); candidate already has another child named Benjamin M. Glasgow (Glasgow-66) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Show complete scoring
  • candidate's birth is 86 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • uncommon given names recur in both otherwise distinct descendant branches: Benjamin +12 (13 public profiles; subject branch: Benjamin Douglas Thomas Glasco; candidate branch: Benjamin M. Glasgow) (+12 total)

Deductions and cautions: chronologically conflicting 60-year parent-child age gap (−8); same country, but no indexed locality overlap (−10); subject lies more than 20 years from the candidate's known child-bearing period (−6; children may be missing); candidate already has another child named Benjamin M. Glasgow (Glasgow-66) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Automated fit28/100
Chronology-Only Fallback
Dates1820–1896Generation40 years age gapRecorded placesWashington, Washington County, IowaIndependent clue breadth · 3Age · Spouse-Specific Child Window · Two-GenerationSame-spouse child windowRobert Barclay GlasgowCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 40-year parent-child age gap (+18)
  • candidate's birth is 66 years before the subject's earliest dated child (1886), 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 40-year parent-child age gap (+18)
  • candidate's birth is 66 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • subject's birth fits between children attributed to the same parental couple (1857–1865) (+6; other parent Robert Barclay Glasgow)

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

Automated fit26/100
Chronology-Only Fallback
Dates1838–1933Generation22 years age gapRecorded placesWest Virginia, United States · Kirksville, Adair, Missouri, United StatesIndependent clue breadth · 4Age · Broad Geography · Household · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 22-year parent-child age gap (+18)
  • candidate's birth is 48 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • a known child was born within 3 years of the subject (+3)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 22-year parent-child age gap (+18)
  • candidate's birth is 48 years before the subject's earliest dated child (1886), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: missouri (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)
  • a known child was born within 3 years of the subject (+3)

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

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.

Same-name candidate

Benjamin GlassgoGlassgo-4

Automated fit43/100
Similar Person
Dates1858–?PlacesNorth Carolina, United StatesParent 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

Open side-by-side comparison
Automated fit38/100
Similar Person
Dates1875–1945PlacesArkansas, United States → Octa, Dunklin, Missouri, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 15 (+2)
  • death years within 1 (+10)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 15 (+2)
  • death years within 1 (+10)
  • overlapping locality (+8)

Conflicts: No indexed conflict

Open side-by-side comparison
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. 1860

Profile-stated birthplace: Morgan County, Indiana, USA

Morgan County, Indiana, USA

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 Glasco-38

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.3 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 Glasco-38
Technical profile and raw captureDataset metadata, machine dossier and captured WikiTree biography.Advanced

WikiTree profile information

Glasco-38

Benjamin Douglas Thomas Glasco

Updated 2022-12-31

Dataset: ONT_Glasco_2026-08-18T16_05.json · generated 2026-08-20

Machine-readable dossier