Glasgow Surname Project

Individual research record

James Glasgow

1793-10-04 – 1875-01-20

Glasgow-2577 · 1 mapped association

Blair County, Pennsylvania, United StatesDeath place unknown

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
2Close relations
2Evidence items
12Candidate leads
Birth
1793-10-04 · Blair County, Pennsylvania, United States
Death
1875-01-20 · Place not recorded
Parents
Not recorded
Spouses
Hannah Turner
Children
Mary Ellen Glasgow
Gender
Male
WikiTree
Glasgow-2577
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 positionMary Ellen Glasgow (1829)
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 fit35/100
Weak Lead
Dates1758–1825Generation35 years age gapRecorded placesGlasgow, Lanarkshire, Scotland · Sinking Valley, Blair, Pennsylvania, United States · GlasgowIndependent clue breadth · 5Age · Household · Local Sibling Birth · Two-Generation · Undated LocalityCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 35-year parent-child age gap (+18)
  • candidate has only broad or undated birth-locality overlap: blair (+6)
  • candidate's birth is 71 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 35-year parent-child age gap (+18)
  • candidate's birth is 71 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • candidate has only broad or undated birth-locality overlap: blair (+6)
  • subject's birth fits within the candidate's overall child-bearing span (1778–1798) (+3; children are not tied to one spouse)
  • candidate has another child, Taylor Wilson Glasgow, born 5 years from the subject in the same specific birth locality (+4; possible sibling-household clue)

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

Automated fit12/100
Weak Lead
Dates1785–1820Generationnominally 8 years; approximate dates permit about 16–18 years age gapRecorded placesLocation not supplied — profile holding pointIndependent clue breadth · 3Age · Same-Sex Generational Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • the nominal 8-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (16–18 years) (+4)
  • candidate's birth is 44 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)

parentage requires the approximate birth estimate to be early enough (no deduction); locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • the nominal 8-year gap is too small, but the approximate birth date permits a narrow biologically viable interval (16–18 years) (+4)
  • candidate's birth is 44 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name James (+4; weak direct parent-child name recurrence, 224 public profiles)

Deductions and cautions: parentage requires the approximate birth estimate to be early enough (no deduction); locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show 3 lower-scoring possible fathers
Automated fit8/100
Weak Lead
Dates1776–1850Generation17 years age gapRecorded placesNorth Carolina, United States · Smith, Tennessee, 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 53 years before the subject's earliest dated child (1829), 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 53 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • candidate and subject share the given name James (+4; weak direct parent-child name recurrence, 224 public profiles)

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

Automated fit8/100
Weak Lead
Dates1748–1812Generation45 years age gapRecorded placesLarne, County Antrim, Ireland · County Antrim — exact locality unprovedIndependent clue breadth · 4Age · Same-Sex Generational Naming · Spouse · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 45-year parent-child age gap (+18)
  • known spouse Jane Glasgow had a plausible maternal age (43) at the subject's birth (+7)
  • candidate's birth is 81 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)

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

Show complete scoring
  • plausible 45-year parent-child age gap (+18)
  • candidate's birth is 81 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • known spouse Jane Glasgow had a plausible maternal age (43) at the subject's birth (+7)
  • candidate and subject share the given name James (+4; weak direct parent-child name recurrence, 224 public profiles)

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

Automated fit6/100
Weak Lead
Dates1735–1819Generation58 years age gapRecorded placesMaryland · Tennessee, United StatesIndependent clue breadth · 5Age · Household · Same-Sex Generational Naming · Spouse · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • known spouse Phereby (Sheppard) Glasgow had a plausible maternal age (45) at the subject's birth (+7)
  • candidate's birth is 94 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • a known child was born within 3 years of the subject (+3)

same country, but no indexed locality overlap (−10); candidate already has another child named James Glasgow (Glasgow-2492) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Show complete scoring
  • less typical 58-year parent-child age gap (+2)
  • candidate's birth is 94 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • same research cluster (+0; grouping is not kinship evidence)
  • a known child was born within 3 years of the subject (+3)
  • known spouse Phereby (Sheppard) Glasgow had a plausible maternal age (45) at the subject's birth (+7)
  • candidate and subject share the given name James (+4; weak direct parent-child name recurrence, 224 public profiles)

Deductions and cautions: same country, but no indexed locality overlap (−10); candidate already has another child named James Glasgow (Glasgow-2492) without a documented death permitting name reuse (−4; check whether the child profiles duplicate or conflict)

Possible mothers5 leads

Automated fit28/100
Chronology-Only Fallback
Dates1765–?Generation28 years age gapRecorded placesLocation not supplied — profile holding pointIndependent clue breadth · 3Age · Spouse-Specific Child Window · Two-GenerationSame-spouse child windowWilliam GlasgowCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 28-year parent-child age gap (+18)
  • candidate's birth is 64 years before the subject's earliest dated child (1829), 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 28-year parent-child age gap (+18)
  • candidate's birth is 64 years before the subject's earliest dated child (1829), 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 (1783–1802) (+6; other parent William 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
Dates1757–1840Generation36 years age gapRecorded placesIreland · Allegheny, Pennsylvania, United States · County Antrim — exact locality unprovedIndependent clue breadth · 4Age · Broad Geography · Household · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 36-year parent-child age gap (+18)
  • candidate's birth is 72 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • a known child was born within 1 years of the subject (+3)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 36-year parent-child age gap (+18)
  • candidate's birth is 72 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: pennsylvania (+1; not a locality match)
  • a known child was born within 1 years of the subject (+3)

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

Show 3 lower-scoring possible mothers
Automated fit23/100
Chronology-Only Fallback
Dates1775–1839Generation18 years age gapRecorded placesPennsylvania · Cadiz, Harrison, Ohio, United StatesIndependent clue breadth · 3Age · Broad Geography · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 18-year parent-child age gap (+18)
  • candidate's birth is 54 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: pennsylvania (+1; not a locality match)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 18-year parent-child age gap (+18)
  • candidate's birth is 54 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: pennsylvania (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)

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

Automated fit23/100
Chronology-Only Fallback
Dates1767–1812Generation26 years age gapRecorded placesNottingham, West Nottingham Township, Chester, PennsylvaniaIndependent clue breadth · 3Age · Broad Geography · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 26-year parent-child age gap (+18)
  • candidate's birth is 62 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: pennsylvania (+1; not a locality match)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 26-year parent-child age gap (+18)
  • candidate's birth is 62 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: pennsylvania (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)

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

Automated fit23/100
Chronology-Only Fallback
Dates1762–1857Generation31 years age gapRecorded placesCecil County, Maryland · Pennsylvania, United StatesIndependent clue breadth · 3Age · Broad Geography · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 31-year parent-child age gap (+18)
  • candidate's birth is 67 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: pennsylvania (+1; not a locality match)

No indexed conflict; documentary proof still required

Show complete scoring
  • plausible 31-year parent-child age gap (+18)
  • candidate's birth is 67 years before the subject's earliest dated child (1829), a compatible grandparent-generation interval (+4)
  • weak broad-area overlap: pennsylvania (+1; not a locality match)
  • same research cluster (+0; grouping is not kinship evidence)

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.

Automated fit49/100
Similar Person
Dates1796–1878PlacesPennsylvania, United States → Crocker, Pulaski, Missouri, United StatesParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • birth years within 3 (+18)
  • death years within 3 (+5)

No indexed conflict

Full comparison detail
  • same first and last name (+18)
  • birth years within 3 (+18)
  • death years within 3 (+5)
  • overlapping locality (+8)

Conflicts: No indexed conflict

Same-name candidate

James GlasgowGlasgow-3095

Automated fit48/100
Similar Person
Dates1793–?PlacesCambusnethan, Lanarkshire, ScotlandParent 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. 1793

Profile-stated birthplace: Blair County, Pennsylvania, United States

Blair County, 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 Glasgow-2577

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
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 Find-a-grave #62188579 (https://www.findagrave.com/memorial/62188579/james-glasgow/)
  2. tree_only WikiTree profile export for Glasgow-2577
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

Glasgow-2577 was captured 2026-08-07T09:54:35+00:00; WikiTree profile revision 2025-07-03.

Profile location claims

EventDateLocationStatus
birthBlair County, Pennsylvania, United StatesWikiTree profile field

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ChildrenMary Ellen GlasgowGlasgow-25781829-02-12 · Blair County, Pennsylvania, United States · 1915-02-28 · Altoona, Blair County, Pennsylvania, United States
SpousesHannahTurner-450941794-03-13 · 1856-01-31 · Blair County, Pennsylvania, United States · 0000-00-00

Profile categories

Logan Valley Cemetery, Bellwood, Pennsylvania Logan_Valley_Cemetery,_Bellwood,_Pennsylvania

Record-bearing passages

Profile source citations

  1. Find-a-grave #62188579 (https://www.findagrave.com/memorial/62188579/james-glasgow/) source link 1
Full captured biography text
Biography
James was born in 1793. He passed away in 1875.
Sources
* Find-a-grave #62188579 (https://www.findagrave.com/memorial/62188579/james-glasgow/)
Raw WikiTree biography markup
[[Category:Logan Valley Cemetery, Bellwood, Pennsylvania]]
== Biography ==

James was born in 1793.  He passed away in 1875.
== Sources ==
<references />
* [https://www.findagrave.com/memorial/62188579/james-glasgow/ Find-a-grave #62188579]