Triple
T15729354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doukid dynasty |
E381299
|
entity |
| Predicate | fallFromPower |
P86927
|
FINISHED |
| Object | coup of Alexios I Komnenos in 1081 |
—
|
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: coup of Alexios I Komnenos in 1081 | Statement: [Doukid dynasty, fallFromPower, coup of Alexios I Komnenos in 1081]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fallFromPower Context triple: [Doukid dynasty, fallFromPower, coup of Alexios I Komnenos in 1081]
-
A.
fellFromPowerIn
Indicates that an entity lost its position of authority or control in a specified place or context at a particular time.
-
B.
lostPower
Indicates that an entity has ceased to have electrical or functional power it previously possessed.
-
C.
lostPowerIn
Indicates that an entity has experienced a loss of electrical or functional power while in or at a specified location or context.
-
D.
lostPowerAfter
Indicates that one entity ceased to have power or electricity following an event associated with another entity.
-
E.
lostPowerThrough
chosen
Indicates that an entity ceased to have power, authority, or control as a result of another specified entity or factor.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb61cb881908b158609c1ccfa1e |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.