Triple
T28540186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mursili I |
E722268
|
entity |
| Predicate | successorStateAfterBabylonSack |
P193829
|
FINISHED |
| Object | Kassite dynasty in Babylon |
—
|
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: Kassite dynasty in Babylon | Statement: [Mursili I, successorStateAfterBabylonSack, Kassite dynasty in Babylon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorStateAfterBabylonSack Context triple: [Mursili I, successorStateAfterBabylonSack, Kassite dynasty in Babylon]
-
A.
statusAfterAssyrianConquest
Indicates the condition or standing of an entity following the Assyrian conquest.
-
B.
reignAsKingOfBabylonEnd
Indicates the time or event at which an individual’s reign as king of Babylon comes to an end.
-
C.
successorAsCaesarOfTheEast
Indicates that one individual became the next holder of the title or role of Caesar of the Eastern Roman Empire after another individual.
-
D.
successorAsGovernorOfDamascus
Indicates that one person became the next governor of Damascus after another person.
-
E.
cededJerusalemBy
Indicates a relationship where control or authority over Jerusalem is formally transferred or surrendered by one party to another.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: April 28, 2026, 3:35 a.m.