Triple
T15700608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLU-116 |
E380582
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | penetrator warhead |
C26414
|
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: penetrator warhead Context triple: [BLU-116, instanceOf, penetrator warhead]
-
A.
specialized explosive device
chosen
A specialized explosive device is a purpose-built charge engineered with specific materials, triggering mechanisms, and blast characteristics to achieve a targeted effect in controlled applications.
-
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.
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.
-
D.
ballistic missile payload system
A ballistic missile payload system is the integrated assembly of warheads, guidance interfaces, deployment mechanisms, and protective structures designed to deliver and release destructive or specialized payloads to a designated target along a ballistic trajectory.
-
E.
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.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:45 a.m.