Triple
T23508686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haditha killings |
E572355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | incident in the Iraq War |
C46374
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: incident in the Iraq War Context triple: [Haditha killings, instanceOf, incident in the Iraq War]
-
A.
battle of the Iraq War
A battle of the Iraq War is a discrete military engagement between opposing forces within the broader 2003–2011 conflict in Iraq, characterized by specific objectives, participants, location, and timeframe.
-
B.
Iraq War–related event
chosen
An Iraq War–related event is any specific occurrence, action, or development directly connected to the planning, conduct, impact, or aftermath of the Iraq War.
-
C.
phase of the Iraq War
A phase of the Iraq War is a distinct period characterized by specific military, political, and social dynamics, objectives, and strategies that differentiate it from other periods of the conflict.
-
D.
event in the Kosovo War
A specific incident, operation, or development that occurred during the Kosovo War, involving military, political, or humanitarian actions and their immediate consequences.
-
E.
event in the Syrian civil war
An event in the Syrian civil war is a specific, temporally and geographically bounded incident—such as a battle, airstrike, protest, ceasefire, or diplomatic action—that significantly affects the course, dynamics, or humanitarian conditions of the conflict.
- F. None of above.
Provenance (1 batch)
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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:07 p.m.