Triple
T795830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Orion (nuclear pulse propulsion) |
E17017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear pulse propulsion system |
C6058
|
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 pulse propulsion system Context triple: [Project Orion (nuclear pulse propulsion), instanceOf, nuclear pulse propulsion system]
-
A.
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.
-
B.
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.
-
C.
fully reusable launch system
A fully reusable launch system is a space launch architecture in which all major components (such as boosters, upper stages, and spacecraft) are recovered, refurbished, and flown again, minimizing expendable hardware and reducing per-launch costs.
-
D.
nuclear reactor
A nuclear reactor is a controlled system that initiates, sustains, and regulates a nuclear fission chain reaction to produce heat, typically for generating electricity or powering ships.
-
E.
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.
- F. None of above. chosen
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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:38 p.m.