Triple
T235233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-2 incident of 1960 |
E4495
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cold War incident |
C37
|
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 incident Context triple: [U-2 incident of 1960, instanceOf, Cold War incident]
-
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 polity
A Cold War polity is a state or political entity whose institutions, policies, and international behavior are fundamentally shaped by the ideological, military, and geopolitical tensions between the U.S.-led Western bloc and the Soviet-led Eastern bloc from roughly 1947 to 1991.
-
C.
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.
-
D.
20th-century conflict
chosen
20th-century conflict encompasses the major wars, revolutions, and geopolitical struggles between 1900 and 1999 that reshaped global power structures, societies, and ideologies.
-
E.
geopolitical conflict
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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.