Triple
T1371446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flexible response doctrine |
E30120
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear deterrence strategy |
C310
|
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: nuclear deterrence strategy Context triple: [flexible response doctrine, instanceOf, nuclear deterrence strategy]
-
A.
nuclear weapons program
A nuclear weapons program is an organized, often state-led effort to research, develop, test, produce, and maintain nuclear warheads and their delivery systems for military deterrence or potential use.
-
B.
nuclear weapon
A nuclear weapon is a highly destructive explosive device that releases immense energy through nuclear fission, fusion, or a combination of both, causing catastrophic blast, heat, and radiation effects.
-
C.
Cold War strategy
chosen
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.
-
D.
nuclear weapons crisis
A nuclear weapons crisis is a high-stakes international confrontation in which the use or threatened use of nuclear arms becomes a realistic possibility, creating urgent risks of catastrophic escalation and intense diplomatic, military, and political pressure to resolve the conflict.
-
E.
nuclear reservation
A nuclear reservation is a designated area of land set aside for the development, testing, production, storage, or decommissioning of nuclear materials and facilities under strict regulatory control.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:57 p.m.