Dated assessments, source transcriptions and earlier working notes remain available in full. Where those disagree, use the current conclusion above and inspect its reasoning.
No separately maintained research assessment in this snapshot. The available records are preserved below.
Life and record timelineChronological mapped occurrences and their underlying sources.1 record
b. 1795
Profile-stated birthplace: Calliaqua, Saint George, Saint Vincent and the Grenadines
Dates1767–1812Generation28 years age gapRecorded placesCochranville, Chester County, Pennsylvania, USAIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
plausible 28-year parent-child age gap (+18)
candidate's birth is 43 years before the subject's earliest dated child (1810), 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 43 years before the subject's earliest dated child (1810), 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)
Dates1761–?Generation34 years age gapRecorded placesLincolnshire, EnglandIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
plausible 34-year parent-child age gap (+18)
candidate's birth is 49 years before the subject's earliest dated child (1810), a compatible grandparent-generation interval (+4)
locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)
Show complete scoring
plausible 34-year parent-child age gap (+18)
candidate's birth is 49 years before the subject's earliest dated child (1810), a compatible grandparent-generation interval (+4)
Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)
Dates1760–?Generation35 years age gapRecorded placesMonkstown, County Dublin, IrelandIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
plausible 35-year parent-child age gap (+18)
candidate's birth is 50 years before the subject's earliest dated child (1810), a compatible grandparent-generation interval (+4)
locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)
Show complete scoring
plausible 35-year parent-child age gap (+18)
candidate's birth is 50 years before the subject's earliest dated child (1810), a compatible grandparent-generation interval (+4)
Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)
Dates1767–1833Generation28 years age gapRecorded placesInishrush, Tamlaght O'Crilly, County Londonderry, Ireland · St Nossonus — Tamlaght O'Crilly Lower graveyardIndependent clue breadth · 4Age · Contemporaneous Household Conflict · Spouse-Specific Child Window · Two-GenerationSame-spouse child windowAdam GlasgowCurrent relationshipNot currently linked as parent
Strongest signals
plausible 28-year parent-child age gap (+18)
candidate's birth is 43 years before the subject's earliest dated child (1810), a compatible grandparent-generation interval (+4)
subject's birth fits between children attributed to the same parental couple (1790–1822) (+6; other parent Adam Glasgow)
locality comparison is unavailable because one or both profiles lack adequate place data (no deduction); candidate's household recorded James Glasgow in Inishrush, Tamlaght O’Crilly, County Londonderry within 1 years of the subject (−12; no contemporaneous child is indexed in the subject's locality)
Show complete scoring
plausible 28-year parent-child age gap (+18)
candidate's birth is 43 years before the subject's earliest dated child (1810), a compatible grandparent-generation interval (+4)
subject's birth fits between children attributed to the same parental couple (1790–1822) (+6; other parent Adam Glasgow)
Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction); candidate's household recorded James Glasgow in Inishrush, Tamlaght O’Crilly, County Londonderry within 1 years of the subject (−12; no contemporaneous child is indexed in the subject's locality)
Dates1750–?Generation45 years age gapRecorded placesLarne, County Antrim, Ireland · County Antrim — exact locality unprovedIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
possible 45-year parent-child age gap (+10)
candidate's birth is 60 years before the subject's earliest dated child (1810), a compatible grandparent-generation interval (+4)
locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)
Show complete scoring
possible 45-year parent-child age gap (+10)
candidate's birth is 60 years before the subject's earliest dated child (1810), a compatible grandparent-generation interval (+4)
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.
No sufficiently similar same-name person is currently indexed.
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.