Glasgow Surname Project

Individual research record

Lillie (Stevens) Glasgow

before 1894 – ?

Stevens-10915 · 1 mapped association

Birthplace unknownDeath place unknown

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
2Close relations
2Evidence items
2Candidate leads
Birth
before 1894 · Place not recorded
Death
Not recorded · Place not recorded
Parents
Not recorded
Spouses
Thomas Glasgow
Children
Edna B (Glasgow) Armstrong
Gender
Female
WikiTree
Stevens-10915
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 positionEdna B (Glasgow) Armstrong (1914)
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 mothers1 leads

Automated fit14/100
Chronology-Only Fallback
Dates1866–1938Generationat most 28 years age gapRecorded placesChicago, Cook, Illinois, United States · Elgin, Kane, Illinois, United StatesIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • candidate's birth is 48 years before the subject's earliest dated child (1914), a compatible grandparent-generation interval (+4)
  • bounded birth date gives a parent-child age gap of at most 28 years (+10; true age remains uncertain)
  • 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
  • bounded birth date gives a parent-child age gap of at most 28 years (+10; true age remains uncertain)
  • candidate's birth is 48 years before the subject's earliest dated child (1914), 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)

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 fit28/100
Similar Person
Dates1886–1982PlacesOskaloosa, Barton, Missouri, United States → Chula Vista, San Diego, California, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 8 (+10)

No indexed conflict

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

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

Kin-inferred from child Edna B (Glasgow) Armstrong’s birthplace: Harris, Arkansas, United States

Harris, Arkansas, United States

One-Tree export profile fields are search leads, not sources; relationships are shown only where the export supplies parent links. This map placement is an estimate from kin and is not a directly recorded location for this person.

Kin-inferred One-Tree profile leadunknown
Source and mapping detail

WikiTree profile export for Stevens-10915

No sufficiently specific citation match found.

Precision: Kin-inferred relationship locality

Evidence assessmentWhat is supported, uncertain or disputed in the current case model.3 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 Information provided by Edna's obituary at www.legacy.com.
  2. tree_only WikiTree profile export for Stevens-10915
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

Stevens-10915 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2016-10-06.

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ChildrenEdna B ArmstrongGlasgow-5711914-03-31 · Harris, AR · 2015-10-17 · Kalkaska, MI
SpousesThomas GlasgowGlasgow-5721894-00-00 · 0000-00-00

Profile source citations

  1. Information provided by Edna's obituary at www.legacy.com.
Full captured biography text
BiographySources
* Information provided by Edna's obituary at www.legacy.com.
Raw WikiTree biography markup
== Biography ==



== Sources ==
<references />
* Information provided by Edna's obituary at www.legacy.com.