Triple
T5982504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nouri al-Maliki |
E133150
|
entity |
| Predicate | leftOfficeReason |
P15987
|
FINISHED |
| Object | Resigned amid political pressure in 2014 |
—
|
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: Resigned amid political pressure in 2014 | Statement: [Nouri al-Maliki, leftOfficeReason, Resigned amid political pressure in 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leftOfficeReason Context triple: [Nouri al-Maliki, leftOfficeReason, Resigned amid political pressure in 2014]
-
A.
officeAbolitionReason
Indicates the reason or justification for abolishing a particular office or official position.
-
B.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an entity.
-
C.
leftOffice
Indicates that an entity ceased holding or performing the duties of a particular office or position.
-
D.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
E.
reasonForLeaving
chosen
Indicates the cause, motivation, or circumstance that led an entity to depart or discontinue an association, position, or place.
- 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_69c0086f45e8819098f73dd16d45ec9d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04a6a9f2c8190b900cd7e3ab9fe42 |
completed | March 22, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69c049de98648190962b14fd341c93da |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:04 p.m.