Triple
T10322235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Saʿid Bahadur Khan |
E242162
|
entity |
| Predicate | consequenceOfDeath |
P76982
|
FINISHED |
| Object | collapse of centralized Mongol authority in Persia |
—
|
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: collapse of centralized Mongol authority in Persia | Statement: [Abu Saʿid Bahadur Khan, consequenceOfDeath, collapse of centralized Mongol authority in Persia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfDeath Context triple: [Abu Saʿid Bahadur Khan, consequenceOfDeath, collapse of centralized Mongol authority in Persia]
-
A.
effectOfDeath
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
B.
deathResultedIn
Indicates that one event, action, or condition caused or led directly to a particular death as its outcome.
-
C.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
D.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
E.
afterDeath
chosen
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:50 a.m.