Triple
T16939617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peaceful Nuclear Explosions Treaty |
E410916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear test limitation treaty |
C566
|
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 test limitation treaty Context triple: [Peaceful Nuclear Explosions Treaty, instanceOf, nuclear test limitation treaty]
-
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.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
D.
nuclear reservation
A nuclear reservation is a designated area of land set aside for the development, testing, production, storage, or decommissioning of nuclear materials and facilities under strict regulatory control.
-
E.
component of CTBT verification regime
A component of the CTBT verification regime is an institutional, technical, or procedural element—such as monitoring systems, data analysis centers, or on-site inspections—that collectively ensure compliance with and detection of nuclear test activities under the Comprehensive Nuclear-Test-Ban Treaty.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.