Triple
T16939666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Nuclear Tests July 1945 through September 1992 (DOE/NV-209) |
E410917
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear testing catalog |
C38273
|
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 testing catalog Context triple: [United States Nuclear Tests July 1945 through September 1992 (DOE/NV-209), instanceOf, nuclear testing catalog]
-
A.
nuclear test
A nuclear test is an experimental detonation or controlled release of nuclear energy conducted to develop, evaluate, or demonstrate the performance and effects of nuclear weapons or technology.
-
B.
nuclear weapons test series
A nuclear weapons test series is an organized sequence of nuclear detonations conducted under a unified program or objective to develop, evaluate, or demonstrate nuclear weapon capabilities.
-
C.
atomic bomb test
An atomic bomb test is a controlled detonation of a nuclear device conducted to evaluate its design, yield, and effects for military, scientific, or political purposes.
-
D.
former nuclear test site
A former nuclear test site is a geographically defined area where nuclear weapons or devices were previously detonated for testing purposes and which may still be subject to environmental monitoring, contamination concerns, and restricted use.
-
E.
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.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.