Glasgow Surname Project

Individual research record

George Glasco

c. 1857 – ?

Glasco-18 · 1 mapped association

District Of ColumbiaDeath place unknown

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
2Close relations
1Evidence items
12Candidate leads
Birth
c. 1857 · District Of Columbia
Death
Not recorded · Place not recorded
Parents
Thomas GlascounmarkedMary (Lyle) Glascounmarked
Spouses
Not recorded
Children
Not recorded
Gender
Male
WikiTree
Glasco-18
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.

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.

Same-name candidate

George W. GlasgowGlasgow-740

Automated fit31/100
Similar Person
Dates1861–?PlacesPennsylvania, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 4 (+18)

unassessed father attachments differ (−5)

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

Conflicts: unassessed father attachments differ (−5)

Same-name candidate

George GlasgowGlasgow-562

Automated fit23/100
Similar Person
Dates1848–?PlacesKendal, Westmorland, England, United KingdomParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 9 (+10)

unassessed father attachments differ (−5)

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

Conflicts: unassessed father attachments differ (−5)

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

Profile-stated birthplace: District Of Columbia

District Of Columbia

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-18

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-18
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