Triple
T33894675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W51 warhead |
E868872
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | thermonuclear warhead design |
C4347
|
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 warhead design Context triple: [W51 warhead, instanceOf, thermonuclear warhead design]
-
A.
nuclear weapon
chosen
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.
-
B.
plutonium implosion-type nuclear bomb
A plutonium implosion-type nuclear bomb is a weapon that uses precisely timed conventional explosives to symmetrically compress a subcritical plutonium core into a supercritical state, initiating a rapid, uncontrolled nuclear chain reaction.
-
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 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.
-
E.
nuclear weapons assembly plant
A nuclear weapons assembly plant is a highly secure industrial facility where nuclear and non-nuclear components are manufactured, integrated, and tested to produce complete nuclear weapons in compliance with strict safety, security, and regulatory standards.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.