Triple
T13816980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet thermonuclear weapons program |
E332044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | thermonuclear weapons program |
C301
|
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: thermonuclear weapons program Context triple: [Soviet thermonuclear weapons program, instanceOf, thermonuclear weapons program]
-
A.
nuclear weapons program
chosen
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.
strategic nuclear weapon
A strategic nuclear weapon is a high-yield nuclear device designed for long-range delivery against an adversary’s key military, industrial, or political targets to achieve large-scale, war-altering effects.
-
D.
nuclear weapons policy
Nuclear weapons policy is the set of principles, laws, strategies, and international agreements that govern the development, deployment, potential use, and control of nuclear weapons by states and organizations.
-
E.
national nuclear energy program
A national nuclear energy program is a coordinated governmental initiative that plans, develops, regulates, and operates nuclear technologies to generate electricity and support related industrial, scientific, and security 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:12 p.m.