Triple
T31209747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dál gCais in Munster kingship |
E795702
|
entity |
| Predicate | replacedDynasty |
P39883
|
FINISHED |
| Object | Eóganachta |
—
|
NE NERFINISHED |
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: Eóganachta | Statement: [Dál gCais in Munster kingship, replacedDynasty, Eóganachta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedDynasty Context triple: [Dál gCais in Munster kingship, replacedDynasty, Eóganachta]
-
A.
dynastyChange
chosen
Indicates a transition in ruling power from one dynasty to another.
-
B.
dynasticNameChangedTo
Indicates that an entity’s dynastic name was replaced by or transitioned into a new dynastic name.
-
C.
replacedRegimeOf
Indicates that one regime has taken the place of or succeeded another regime in power or authority.
-
D.
dynastyRestored
Indicates that a previously displaced ruling dynasty has been returned to power or reestablished as the legitimate authority.
-
E.
dynasticSuccessionChangedBy
Indicates that a change or disruption has occurred in the established line of dynastic succession due to the influence or action of the related entity.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 29, 2026, 9:09 p.m.