Triple
T7086460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Storm |
E165087
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Croatian military operation |
C340
|
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: Croatian military operation Context triple: [Operation Storm, instanceOf, Croatian military operation]
-
A.
military operation
chosen
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
B.
Ottoman–Serbian battle
An Ottoman–Serbian battle is a military engagement fought between forces of the Ottoman Empire and the Serbian state or Serbian-led armies, typically occurring during the medieval and early modern periods in the Balkans.
-
C.
Cold War operation
A Cold War operation is a covert or overt mission conducted by a state or its proxies during the Cold War era to advance strategic, ideological, or geopolitical objectives without escalating into full-scale direct conflict between superpowers.
-
D.
Habsburg–Ottoman War
The Habsburg–Ottoman War is a conceptual class representing the series of military conflicts between the Habsburg Monarchy and the Ottoman Empire, encompassing their political, territorial, and religious struggles across Central and Eastern Europe from the 16th to the 18th centuries.
-
E.
battle of the Long Turkish War
A battle of the Long Turkish War is a specific military engagement fought between Habsburg and Ottoman forces (and their allies) during the protracted conflict in Central and Eastern Europe from 1593 to 1606.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:41 p.m.