Glasgow Surname Project

Individual research record

Phillip Glasco

c. 1715 – after 1772

Glasco-146 · 1 mapped association

Birthplace unknown→County Dublin, Ireland
View on mapOpen WikiTreeCompareReport a correction

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
4Close relations
1Evidence items
11Candidate leads
Birth
c. 1715 · Place not recorded
Death
after 1772 · County Dublin, Ireland
Parents
Not recorded
Spouses
Catherine (Mangan) GlascoMary (Braccan) Glasco
Children
James GlascoPhillip Glasco
Gender
Male
WikiTree
Glasco-146
Research clusters
Ireland One-Tree profile leads
Mapped descendants
4

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 positionJames Glasco (1730)
Maternal grandfather positionPhillip Glasco (1740)
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

Possible fathers5 leads

Automated fit47/100
Moderate Lead
Dates1671–?Generation44 years age gapRecorded placesLinlithgow, Linlithgowshire, Scotland · Ayrshire, Scotland · LinlithgowIndependent clue breadth · 5Age · Collateral Naming · Spouse · Spouse-Specific Child Window · Two-GenerationSame-spouse child windowMary (Gemill) GlasgowCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 44-year parent-child age gap (+18)
  • candidate's birth is 59 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • known spouse Mary (Gemill) Glasgow had a bounded, possibly plausible maternal age (29) at the subject's birth (+3)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 44-year parent-child age gap (+18)
  • candidate's birth is 59 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • subject's birth fits between children attributed to the same parental couple (1707–1726) (+6; other parent Mary (Gemill) Glasgow)
  • known spouse Mary (Gemill) Glasgow had a bounded, possibly plausible maternal age (29) at the subject's birth (+3)
  • candidate's sibling and niece/nephew network repeats names in the subject's descendant line (three rarest at most): Philip +16 (2 public profiles; niece/nephew Philip Glasgow) (+16 total)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Automated fit34/100
Weak Lead
Dates1675–?Generationat least 40 years age gapRecorded placesLinlithgow, Linlithgowshire, Scotland · LinlithgowIndependent clue breadth · 5Age · Household · Rare Branch-Name Recurrence · Spouse · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • candidate's birth is 55 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • known spouse Jean Glasgow had a bounded, possibly plausible maternal age (23) at the subject's birth (+3)
  • a known child was born within 4 years of the subject (+1)

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 least 40 years (+10; true age remains uncertain)
  • candidate's birth is 55 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • a known child was born within 4 years of the subject (+1)
  • known spouse Jean Glasgow had a bounded, possibly plausible maternal age (23) at the subject's birth (+3)
  • uncommon given names recur in both otherwise distinct descendant branches: Phillip +16 (6 public profiles; subject branch: Phillip Glasco, Phillip Glasco; candidate branch: Phillip Glasgow; +2 repetition bonus) (+16 total)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show 3 lower-scoring possible fathers
Automated fit33/100
Weak Lead
Dates1679–?Generation36 years age gapRecorded placesEdinburgh, Midlothian, Scotland · EdinburghIndependent clue breadth · 4Age · Sex-Aware Ordered Naming · Spouse · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 36-year parent-child age gap (+18)
  • known spouse Jean (Dobie) Glasgow had a plausible maternal age (35) at the subject's birth (+7)
  • candidate's birth is 51 years before the subject's earliest dated child (1730), 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 36-year parent-child age gap (+18)
  • candidate's birth is 51 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • known spouse Jean (Dobie) Glasgow had a plausible maternal age (35) at the subject's birth (+7)
  • candidate's name matches the first dated son James Glasco, the expected father position for a male subject (+4; catalogue rarity 0, James in 224 profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Automated fit29/100
Weak Lead
Dates1688–?Generation27 years age gapRecorded placesKirknewton, Linlithgowshire, Scotland · Kirknewton — West LothianIndependent clue breadth · 4Age · Household · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 27-year parent-child age gap (+18)
  • candidate's birth is 42 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • subject's birth fits within the candidate's overall child-bearing span (1714–1717) (+3; children are not tied to one spouse)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 27-year parent-child age gap (+18)
  • candidate's birth is 42 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • subject's birth fits within the candidate's overall child-bearing span (1714–1717) (+3; children are not tied to one spouse)
  • candidate's name matches the first dated son James Glasco, the expected father position for a male subject (+4; catalogue rarity 0, James in 224 profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Automated fit29/100
Weak Lead
Dates1670–?Generation45 years age gapRecorded placesKilwinning, Ayrshire, Scotland · Kilwinning — AyrshireIndependent clue breadth · 4Age · Sex-Aware Ordered Naming · Spouse · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 45-year parent-child age gap (+18)
  • candidate's birth is 60 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • known spouse Margaret (Park) Glasgow had a bounded, possibly plausible maternal age (45) at the subject's birth (+3)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 45-year parent-child age gap (+18)
  • candidate's birth is 60 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • known spouse Margaret (Park) Glasgow had a bounded, possibly plausible maternal age (45) at the subject's birth (+3)
  • candidate's name matches the first dated son James Glasco, the expected father position for a male subject (+4; catalogue rarity 0, James in 224 profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Possible mothers5 leads

Automated fit30/100
Weak Lead
Dates1668–?Generationat least 47 years age gapRecorded placesLinlithgow, Linlithgowshire, Scotland · LinlithgowIndependent clue breadth · 3Age · Collateral Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • candidate's birth is 62 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • bounded birth date gives a parent-child age gap of at least 47 years (+10; true age remains uncertain)
  • candidate's sibling and niece/nephew network repeats names in the subject's descendant line (three rarest at most): Philip +16 (2 public profiles; niece/nephew Philip Glasgow) (+16 total)

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 least 47 years (+10; true age remains uncertain)
  • candidate's birth is 62 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • candidate's sibling and niece/nephew network repeats names in the subject's descendant line (three rarest at most): Philip +16 (2 public profiles; niece/nephew Philip Glasgow) (+16 total)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Automated fit28/100
Weak Lead
Dates1692–?Generationat least 23 years age gapRecorded placesLinlithgowshire / West Lothian — exact locality unprovedIndependent clue breadth · 4Age · Household · Rare Branch-Name Recurrence · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • candidate's birth is 38 years before the subject's earliest dated child (1730), a marginal two-generation interval (+1)
  • a known child was born within 4 years of the subject (+1)
  • bounded birth date gives a parent-child age gap of at least 23 years (+10; true age remains uncertain)

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 least 23 years (+10; true age remains uncertain)
  • candidate's birth is 38 years before the subject's earliest dated child (1730), a marginal two-generation interval (+1)
  • a known child was born within 4 years of the subject (+1)
  • uncommon given names recur in both otherwise distinct descendant branches: Phillip +16 (6 public profiles; subject branch: Phillip Glasco, Phillip Glasco; candidate branch: Phillip Glasgow; +2 repetition bonus) (+16 total)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show 3 lower-scoring possible mothers
Automated fit25/100
Weak Lead
Dates1690–?Generation25 years age gapRecorded placesSkirling, Peeblesshire, Scotland, United Kingdom · Skirling — PeeblesshireIndependent clue breadth · 3Age · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 25-year parent-child age gap (+18)
  • candidate's birth is 40 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • a candidate spouse matches the first dated son James Glasco, the expected father position (+3; James in 224 profiles)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 25-year parent-child age gap (+18)
  • candidate's birth is 40 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • a candidate spouse matches the first dated son James Glasco, the expected father position (+3; James in 224 profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Automated fit25/100
Weak Lead
Dates1680–?Generation35 years age gapRecorded placesEdinburghIndependent clue breadth · 3Age · Sex-Aware Ordered Naming · 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 (1730), a compatible grandparent-generation interval (+4)
  • a candidate spouse matches the first dated son James Glasco, the expected father position (+3; James in 224 profiles)

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 (1730), a compatible grandparent-generation interval (+4)
  • a candidate spouse matches the first dated son James Glasco, the expected father position (+3; James in 224 profiles)

Deductions and cautions: locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Automated fit25/100
Weak Lead
Dates1678–1755Generation37 years age gapRecorded placesIreland · Ireland — exact locality unprovedIndependent clue breadth · 3Age · Sex-Aware Ordered Naming · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • plausible 37-year parent-child age gap (+18)
  • candidate's birth is 52 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • a candidate spouse matches the first dated son James Glasco, the expected father position (+3; James in 224 profiles)

locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • plausible 37-year parent-child age gap (+18)
  • candidate's birth is 52 years before the subject's earliest dated child (1730), a compatible grandparent-generation interval (+4)
  • a candidate spouse matches the first dated son James Glasco, the expected father position (+3; James in 224 profiles)

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.

Same-name candidate

Phillip GlasgowGlasgow-3932

Automated fit38/100
Similar Person
Dates1750–?PlacesCounty Dublin, IrelandParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • shared recorded place (+20)

record-derived birth estimates differ by 35; retained without deduction

Full comparison detail
  • same first and last name (+18)
  • shared recorded place (+20)

Conflicts: record-derived birth estimates differ by 35; retained without deduction

Open side-by-side comparison
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. 1715

Profile-stated death place: County Dublin, Ireland

County Dublin, Ireland

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

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.5 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-146
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