Triple
T9598764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Danube |
E231797
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Warsaw Pact 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: Warsaw Pact military operation Context triple: [Operation Danube, instanceOf, Warsaw Pact military operation]
-
A.
organ of the Warsaw Pact
An organ of the Warsaw Pact is an institutional body established under the Warsaw Treaty Organization to coordinate and implement the alliance’s political, military, or administrative functions among member states.
-
B.
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.
-
C.
Warsaw Pact body
A Warsaw Pact body is an organizational entity, such as a committee, command structure, or coordinating institution, established under the Warsaw Pact to manage its military, political, or administrative functions among member states.
-
D.
Soviet campaign
A Soviet campaign is a coordinated series of military, political, or propaganda operations conducted by the Soviet Union to achieve strategic objectives over a defined period and theater.
-
E.
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.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:07 p.m.