Triple
T12923244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahdi Army |
E309175
|
entity |
| Predicate | notableCeasefire |
P40461
|
FINISHED |
| Object | 2007–2008 ceasefire |
—
|
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: 2007–2008 ceasefire | Statement: [Mahdi Army, notableCeasefire, 2007–2008 ceasefire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCeasefire Context triple: [Mahdi Army, notableCeasefire, 2007–2008 ceasefire]
-
A.
announcedCeasefire
Indicates that an entity has formally declared the suspension of hostilities or fighting, typically within a conflict or war.
-
B.
hasCeasefire
chosen
Indicates that a formal agreement has been established to temporarily stop hostilities or armed conflict between the involved parties.
-
C.
ceasefireDeclared
Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
-
D.
endedCeasefire
Indicates that a previously established ceasefire between parties has been terminated or broken.
-
E.
calledCeasefire
Indicates that an agreement has been made to temporarily stop hostilities or fighting between the involved parties.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e9576c81908eb59569af6da877 |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.