{"schema_version":"1.0","id":"Kelly-21468","alternate_ids":[],"catalogue_id":"kelly-21468","name":"James Kelly","canonical_url":"https://glasgow.phenotype.dev/people/kelly-21468.html","json_url":"https://glasgow.phenotype.dev/people/kelly-21468.json","network_url":"https://glasgow.phenotype.dev/people/kelly-21468.network.json","wikitree_url":"https://www.wikitree.com/wiki/Kelly-21468","vitals":{"birth":{"date":"c. 1841 (estimated)","place":null,"status":"estimated"},"death":{"date":null,"place":null,"status":null}},"identity":{"gender":"Male","occupations":[],"locations":[],"aliases":[],"research_clusters":[]},"relationships":{"parents":[],"spouses":[],"children":[],"siblings":[]},"claims":[{"id":"C-8be38324f241","type":"recorded_occurrence","subject_ids":["Kelly-21468"],"claim":"James Kelly was recorded in an unspecified place (1859).","status":"proved","status_label":"Documented","evidence_ids":["E-8be38324f241"],"notes":"Marriage record","provenance":"mapped_record"}],"evidence":[{"id":"E-8be38324f241","claim_ids":["C-8be38324f241"],"record_type":"Marriage record","date":"1859","place":null,"subjects":["Kelly-21468"],"assertion":"Marriage record","evidence_status":"direct","source_quality":"derivative","independence_group":"SRC-d9bd365627c4","source":{"title":"Scotland, Marriages, 1561-1910","repository":null,"reference":"6ca8d45531ede690","url":"https://www.familysearch.org/ark:/61903/1:1:XTYX-59W"},"provenance":"marriage-index"}],"open_questions":[],"research_leads":[],"source_summary":[{"title":"Scotland, Marriages, 1561-1910","url":"https://www.familysearch.org/ark:/61903/1:1:XTYX-59W","source_quality":"derivative","independence_group":"SRC-d9bd365627c4","provenance":"marriage-index"}],"warnings":[],"provenance":{"tree":"WikiTree One-Tree export","mapped_records":"Glasgow Surname Project map dataset","profile_capture":"Public WikiTree profile evidence capture","relationship_assessments":"Controlled local relationship hypothesis register","research_findings":"Durable research/<profile-or-catalogue-ID>/findings.md case file"},"research_findings":[{"profile_id":"Kelly-21468","updated":null,"source_path":"research/Kelly-21468/findings.md","sections":[{"title":"Current conclusion","category":"conclusion","markdown":"FamilySearch `9Q6K-V3F` matches this WikiTree family through Marion Young and the named children. The reviewed 23 December 1859 Glasgow marriage record names James's spouse Marion Brown but contains no parent fields. The later child records establish James as father, not his own parentage."},{"title":"Recommended action","category":"actions","markdown":"Do not add James Kelly (`9Q6K-JHS`) or Ann Lindsay (`K8TT-GM3`) without a baptism, marriage allegation, or other record naming James's parents."}]}],"similar_people":[],"potential_parentage":{"children_recorded":[],"earliest_dated_son":null,"earliest_dated_daughter":null,"second_dated_son":null,"second_dated_daughter":null,"third_dated_son":null,"third_dated_daughter":null,"naming_controls":{"matches":0,"mismatches":0,"factor":1.0,"details":[]},"candidates":[],"method":"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.","warning":"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."}}