Triple
T78753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuban Missile Crisis |
E1579
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cold War confrontation |
C543
|
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: Cold War confrontation Context triple: [Cuban Missile Crisis, instanceOf, Cold War confrontation]
-
A.
Cold War strategy
Cold War strategy is the overarching approach nations used to pursue geopolitical objectives through deterrence, proxy conflicts, ideological competition, and diplomatic maneuvering without escalating into direct large-scale war between nuclear-armed superpowers.
-
B.
Cold War policy
Cold War policy refers to the strategic, political, military, and economic decisions and doctrines adopted by states—primarily the United States and the Soviet Union—to contain, compete with, or influence each other and their allies without escalating into direct large-scale war.
-
C.
20th-century conflict
20th-century conflict encompasses the major wars, revolutions, and geopolitical struggles between 1900 and 1999 that reshaped global power structures, societies, and ideologies.
-
D.
European war
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
-
E.
geopolitical conflict
chosen
A geopolitical conflict is a sustained struggle between nations or political entities driven by competing interests over territory, resources, ideology, or influence on the global stage.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.