Glasgow Surname Project

Individual research record

Ann Glasgow

1711 – 1786-06-08

Unknown-763010 · 1 mapped association

Birthplace unknownDeath place unknown

At a glance

Identity & family

Tree links organise the family; documentary status still varies.

1Mapped records
6Close relations
2Evidence items
3Candidate leads
Birth
1711 · Place not recorded
Death
1786-06-08 · Place not recorded
Parents
Not recorded
Spouses
Hugh Glasgow
Children
Hugh GlasgowJames GlasgowJean GlasgowMary GlasgowRose Glasgow
Gender
Female
WikiTree
Unknown-763010
Research clusters
Ireland One-Tree profile leads
Mapped descendants
6

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 positionHugh Glasgow (1745)
Maternal grandfather positionJames Glasgow (1748)
Maternal grandmother positionJean Glasgow (1731)
Paternal grandmother positionRose Glasgow (1735)

Known-position checks: 0 support · 1 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 fit0/100
Chronology-Only Fallback
Dates1660–?Generation51 years age gapRecorded placesStirlingshire, Scotland · Stirlingshire — exact locality unprovedIndependent clue breadth · 2Age · Two-GenerationCurrent relationshipNot currently linked as parent
Strongest signals
  • candidate's birth is 71 years before the subject's earliest dated child (1731), a compatible grandparent-generation interval (+4)

chronologically conflicting 51-year parent-child age gap (−8); locality comparison is unavailable because one or both profiles lack adequate place data (no deduction)

Show complete scoring
  • candidate's birth is 71 years before the subject's earliest dated child (1731), a compatible grandparent-generation interval (+4)

Deductions and cautions: chronologically conflicting 51-year parent-child age gap (−8); 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 fit42/100
Similar Person
Dates1766–1784PlacesPlaces not recordedParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • death years within 2 (+10)
  • matching child name: James Glasgow

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

Full comparison detail
  • same first and last name (+18)
  • death years within 2 (+10)
  • matching child name: James Glasgow

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

Automated fit32/100
Similar Person
Dates1670–?PlacesScotland → Derryloran, County Tyrone, Northern Ireland, United KingdomParent comparisonNo shared parent is indexed
Why it may fit
  • same first and last name (+18)
  • matching child name: James Glasgow

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

Full comparison detail
  • same first and last name (+18)
  • matching child name: James Glasgow

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

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

Latest case researchThe current conclusion from the durable research case file.Updated

Current conclusion

Unknown-763010 · updated 2026-08-09

The Larne Parish Churchyard memorial explicitly names Ann Glasgow as wife of Hugh Glasgow-1503. She died 8 June 1786 aged 75, placing her calculated birth between 9 June 1710 and 8 June 1711. Her maiden surname, parents, marriage and birthplace remain unknown.

Jane should not be attached as Hugh's second wife from this monument. The stone uses Jane for a deceased child and for the wife of Hugh and Ann's son James.

Life and record timelineChronological mapped occurrences and their underlying sources.1 record
b. 1711

Kin-inferred from spouse Hugh Glasgow’s birthplace: Larne, County Antrim, Ireland

County Antrim — exact locality unproved

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 Unknown-763010

No sufficiently specific citation match found.

Precision: Kin-inferred relationship locality

Evidence assessmentWhat is supported, uncertain or disputed in the current case model.7 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 A memorial gives Hugh’s death as 8 July 1767 aged 62, implying birth c.1704/05, and names wife Ann.
  2. tree_only WikiTree profile export for Unknown-763010
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

Unknown-763010 was captured 2026-08-11T11:27:28+00:00; WikiTree profile revision 2026-08-11.

Immediate relationship snapshot

RelationshipPersonWikiTree IDDates and places returned
ChildrenJean GlasgowGlasgow-15061731-00-00 · County Antrim, Ireland · 1733-01-08
ChildrenRose GlasgowGlasgow-15071735-00-00 · County Antrim, Ireland · 0000-00-00
ChildrenMary GlasgowGlasgow-15081736-00-00 · County Antrim, Ireland · 0000-00-00
ChildrenHugh GlasgowGlasgow-15101745-00-00 · County Antrim · 1756-00-00
ChildrenJames GlasgowGlasgow-39911748-00-00 · Larne, County Antrim, Ireland · 1812-00-00
SpousesHugh GlasgowGlasgow-15031705-00-00 · Larne, County Antrim, Ireland · 1767-07-08 · 0000-00-00

Record-bearing passages

Profile source citations

  1. A memorial gives Hugh’s death as 8 July 1767 aged 62, implying birth c.1704/05, and names wife Ann.

Other external links in the profile

Full captured biography text
Biography
Ann was born in 1705. 
Sources
* A memorial gives Hugh’s death as 8 July 1767 aged 62, implying birth c.1704/05, and names wife Ann.

[Bigger and Hughes, Larne Parish Churchyard inscriptions](https://archive.org/stream/ulsterjournalofa06ulstiala/ulsterjournalofa06ulstiala_djvu.txt), published 1899 | Ann Glasgow, wife of Hugh Glasgow, died 8 June 1786 aged 75.
Raw WikiTree biography markup
== Biography ==

Ann was born in 1705. 
== Sources ==
<references />
* A memorial gives Hugh’s death as 8 July 1767 aged 62, implying birth c.1704/05, and names wife Ann.

[Bigger and Hughes, Larne Parish Churchyard inscriptions](https://archive.org/stream/ulsterjournalofa06ulstiala/ulsterjournalofa06ulstiala_djvu.txt), published 1899 | Ann Glasgow, wife of Hugh Glasgow, died 8 June 1786 aged 75.