Triple
T12552930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Medina Ridge |
E300139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engagement of the Gulf War |
C31639
|
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: engagement of the Gulf War Context triple: [Battle of Medina Ridge, instanceOf, engagement of the Gulf War]
-
A.
engagement of the Falklands War
The engagement of the Falklands War is a military operation or battle between British and Argentine forces during the 1982 conflict over the Falkland Islands, characterized by specific objectives, participating units, tactics, and outcomes within the broader campaign.
-
B.
engagement of the Korean War
The engagement of the Korean War is a military operation or battle episode involving armed forces of opposing sides during the 1950–1953 conflict on the Korean Peninsula, characterized by direct combat, maneuver, and tactical interaction within a defined time and area.
-
C.
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.
-
D.
Iran–Iraq War
The Iran–Iraq War was a protracted and brutal conflict between Iran and Iraq from 1980 to 1988, marked by trench warfare, chemical weapons, and massive casualties, that reshaped regional politics in the Middle East.
-
E.
Iran–Iraq War battle
An Iran–Iraq War battle is a specific military engagement between Iranian and Iraqi forces that occurred during the Iran–Iraq War from 1980 to 1988.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:58 p.m.