Triple
T31258038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eóganachta dynasty |
E797033
|
entity |
| Predicate | usedSuccessionSystem |
P171639
|
FINISHED |
| Object | tanistry |
—
|
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: tanistry | Statement: [Eóganachta dynasty, usedSuccessionSystem, tanistry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSuccessionSystem Context triple: [Eóganachta dynasty, usedSuccessionSystem, tanistry]
-
A.
governedSuccessionOf
Indicates a succession relationship in which one entity follows another under an established governing rule, law, or authority.
-
B.
successionRitual
Indicates a ritual or ceremonial process through which authority, leadership, or status is formally transferred from one entity to another.
-
C.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
-
D.
supportedSuccessionOf
Indicates that one entity actively endorsed or helped bring about the transfer of power, position, or role from a predecessor to a successor.
-
E.
involvesSuccession
Indicates that one entity follows or replaces another in a sequence, role, or state as part of a succession relationship.
- F. None of above. chosen
Provenance (4 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 9:12 p.m.