Triple
T8246488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | demon core |
E192861
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | plutonium core |
C4348
|
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: plutonium core Context triple: [demon core, instanceOf, plutonium core]
-
A.
plutonium production reactor
A plutonium production reactor is a nuclear reactor specifically designed and operated to irradiate uranium fuel and efficiently generate plutonium-239 for use in nuclear weapons or reactor fuel.
-
B.
plutonium implosion-type nuclear bomb
chosen
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.
weapons-grade plutonium production facility
A weapons-grade plutonium production facility is an industrial complex designed to produce, extract, and process plutonium with isotopic compositions suitable for use in nuclear weapons.
-
D.
uranium processing facility
A uranium processing facility is an industrial plant where uranium ore is refined, converted, and prepared into nuclear-grade materials for use in fuel production or other nuclear applications.
-
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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:48 p.m.