Triple
T24184923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zauditu |
E599529
|
entity |
| Predicate | succeededByInDynasty |
P124532
|
FINISHED |
| Object | Haile Selassie |
—
|
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: Haile Selassie | Statement: [Zauditu, succeededByInDynasty, Haile Selassie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededByInDynasty Context triple: [Zauditu, succeededByInDynasty, Haile Selassie]
-
A.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
B.
successorDynastyOrigin
Indicates the place or cultural-geographic origin from which a successor dynasty arises in relation to its predecessor.
-
C.
successorDynastiesContext
Indicates that one dynasty historically follows and replaces another within a specific contextual framework (such as region, period, or political setting).
-
D.
successorDynastyContinuity
Indicates that one dynasty directly continues or succeeds another in a continuous line of rule or authority.
-
E.
successorDynasticContext
chosen
Indicates that one entity becomes the next holder of power, title, or position in a dynastic or hereditary succession context.
- 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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:35 p.m.