Triple
T37211081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griogair |
E922303
|
entity |
| Predicate | inClanGenealogy |
P134637
|
FINISHED |
| Object | MacGregor lineage |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: MacGregor lineage | Statement: [Griogair, inClanGenealogy, MacGregor lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inClanGenealogy Context triple: [Griogair, inClanGenealogy, MacGregor lineage]
-
A.
genealogicalFunction
Indicates a genealogical relationship or role that one entity holds in relation to another within a family or ancestry structure.
-
B.
clanInheritance
Indicates that rights, titles, or property are passed down within a clan according to its internal rules of succession.
-
C.
clanFamilyOf
chosen
Indicates that one entity belongs to, descends from, or is otherwise affiliated with the same clan or extended family group as another entity.
-
D.
inGenealogyBetween
Indicates that one entity is positioned between two others within a genealogical or family-relationship chain.
-
E.
genealogicalDocumentation
Indicates that there exists recorded evidence or documentation establishing a genealogical relationship between entities.
- F. None of above.
Provenance (3 batches)
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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.