Triple
T22487935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iraq War documents leak |
E555940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iraq War–related event |
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: Iraq War–related event Context triple: [Iraq War documents leak, instanceOf, Iraq War–related event]
-
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.
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.
-
C.
engagement of the Gulf War
The engagement of the Gulf War refers to the series of military operations, battles, and strategic maneuvers conducted by coalition and Iraqi forces during the 1990–1991 conflict in and around the Persian Gulf region.
-
D.
event in the War in Afghanistan (2001–2021)
An event in the War in Afghanistan (2001–2021) is a specific, temporally and geographically bounded occurrence—such as a battle, operation, attack, negotiation, or political decision—that significantly influenced the course, conduct, or consequences of the conflict.
-
E.
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.
- F. None of above. chosen
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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:49 p.m.