Triple
T8807045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Register of All Genealogies and Birthbrieves in Scotland |
E209557
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | genealogical register |
C13899
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: genealogical register Context triple: [Public Register of All Genealogies and Birthbrieves in Scotland, instanceOf, genealogical register]
-
A.
genealogist
A genealogist is a specialist who researches, analyzes, and documents family histories and ancestral lineages using historical records, genetic data, and archival sources.
-
B.
genealogical research institution
A genealogical research institution is an organization that collects, preserves, and analyzes historical records and family data to help individuals and scholars trace lineage, understand ancestry, and study family histories.
-
C.
vital record
A vital record is an official government document that records key life events of individuals, such as births, deaths, marriages, and divorces, for legal and statistical purposes.
-
D.
archival record
chosen
An archival record is a preserved document or item, created or received in the course of activities, maintained as evidence of those activities and retained for its enduring informational, legal, or historical value.
-
E.
cataloging record
A cataloging record is a structured set of metadata describing a resource (such as a book, media item, or digital object) to enable its identification, organization, and retrieval within a catalog or information system.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca836320e48190b5cf585b90a322c4 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:45 p.m.