Glasgow Surname Project

Individual research record

Beulah Christine (Alexander) Glasgow

1910-01-04 – 2012-03-29

Alexander-30730 · 1 mapped association

Neelyville, Butler, Missouri, United StatesHighland, North Township, Lake, Indiana, United States

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
0Close relations
2Evidence items
2Candidate leads
Birth
1910-01-04 · Neelyville, Butler, Missouri, United States
Death
2012-03-29 · Highland, North Township, Lake, Indiana, United States
Parents
Not recorded
Spouses
Not recorded
Children
Not recorded
Gender
Female
WikiTree
Alexander-30730
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
  • 2 parent references point outside the current 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 fit43/100
Similar Person
Dates1912–2004PlacesOklahoma, United States → Oklahoma, 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

Same-name candidate

Beulah (Ash) GlascoAsh-3232

Automated fit28/100
Similar Person
Dates1898–?PlacesWest Mansfield, Bokescreek Township, Logan, Ohio, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 12 (+2)
  • overlapping locality (+8)

No indexed conflict

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

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

Profile-stated birthplace: Neelyville, Butler, Missouri, United States

Neelyville, Butler, Missouri, 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 Alexander-30730

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.1 claim
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
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

Alexander-30730 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2025-09-18.

Profile location claims

EventDateLocationStatus
birthNeelyville, Butler, Missouri, United StatesWikiTree profile field
deathHighland, North Township, Lake, Indiana, United StatesWikiTree profile field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ParentsEdwardAlexander-293261881-08-05 · Neelyville, Butler, Missouri, United States · 1968-11-17 · Schneider, West Creek Township, Lake, Indiana, United States
ParentsMinnieAnderson-922641889-04-13 · Missouri City, Fort Bend, Texas, United States · 1960-09-17 · Schneider, West Creek Township, Lake, Indiana, United States
SiblingsWilliamAlexander-307291908-02-17 · Neelyville, Butler, Missouri, United States · 1995-10-21 · Washington, Illinois, United States
SiblingsFlorenceAlexander-307271912-04-06 · Neelyville, Butler, Missouri, United States · 1989-05-23 · Sheridan, Hamilton, Indiana, United States
SiblingsLeoAlexander-307131914-09-22 · Neelyville, Butler, Missouri, United States · 1971-05-19 · St Louis, St Louis, Missouri, United States
SiblingsJamesAlexander-307321916-03-07 · Neelyville, Butler, Missouri, United States · 1967-06-24 · Camargo, Douglas, Illinois, United States
SiblingsRosalineAlexander-307311922-05-11 · Poplar Bluff, Butler, Missouri, USA · 2020-02-22 · Benton, Franklin, Illinois, USA
SiblingsDickAlexander-243161936-05-21 · Neelyville, Butler, Missouri, United States · 2009-01-01 · Indianapolis, Marion, Indiana, United States

Profile categories

Sanders Cemetery, Lowell, Indiana Sanders_Cemetery,_Lowell,_Indiana

Record-bearing passages

  • Birth: :4 Jan 1910 in Neelyville, Butler, Missouri, USA
  • Marriage: :Abt 1930 in location unknown :Spouse: Earl Lafayette Glasgow (1903 - 1967)
  • Death: :29 Mar 2012 (aged 102) in Highland, Lake, Indiana, USA
  • Burial: :Sanders Cemetery, Lowell, Lake County, Indiana, USA Sources

Profile source citations

  1. Find a Grave Memorial ID: 87699749 for Beulah Christine (Alexander) Glasgow (https://www.findagrave.com/memorial/87699749/beulah-christine-glasgow) source link 1
Full captured biography text
Biography
Name: 
:Beulah Christine (Alexander) Glasgow

Birth:
:4 Jan 1910 in Neelyville, Butler, Missouri, USA

Marriage:
:Abt 1930 in location unknown
:Spouse: Earl Lafayette Glasgow (1903 - 1967)

Death:
:29 Mar 2012 (aged 102) in Highland, Lake, Indiana, USA

Burial:
:Sanders Cemetery, Lowell, Lake County, Indiana, USA
Sources
* Find a Grave Memorial ID: 87699749 for Beulah Christine (Alexander) Glasgow (https://www.findagrave.com/memorial/87699749/beulah-christine-glasgow)
Raw WikiTree biography markup
[[Category:Sanders Cemetery, Lowell, Indiana]]
== Biography ==
'''Name:''' 
:Beulah Christine (Alexander) Glasgow

'''Birth:'''
:4 Jan 1910 in Neelyville, Butler, Missouri, USA

'''Marriage:'''
:Abt 1930 in location unknown
:Spouse: Earl Lafayette Glasgow (1903 - 1967)

'''Death:'''
:29 Mar 2012 (aged 102) in Highland, Lake, Indiana, USA

'''Burial:'''
:Sanders Cemetery, Lowell, Lake County, Indiana, USA

== Sources ==

<references />

* [https://www.findagrave.com/memorial/87699749/beulah-christine-glasgow Find a Grave Memorial ID: 87699749 for Beulah Christine (Alexander) Glasgow]