Triple
T38226349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fall of Mosul (2014) |
E1012156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the Iraq conflict |
C52451
|
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: event in the Iraq conflict Context triple: [Fall of Mosul (2014), instanceOf, event in the Iraq conflict]
-
A.
Iraq War–related event
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.
-
B.
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.
-
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.
battle of the War in Iraq (2013–2017)
chosen
A "battle of the War in Iraq (2013–2017)" is a discrete military engagement or campaign between Iraqi and allied forces and opposing armed groups, occurring within Iraq during the 2013–2017 phase of the conflict, characterized by defined participants, location, timeframe, and strategic objectives.
-
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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.