Triple
T1911662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intermediate-Range Nuclear Forces Treaty |
E38123
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear weapons 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 weapons treaty Context triple: [Intermediate-Range Nuclear Forces Treaty, instanceOf, nuclear weapons treaty]
-
A.
nuclear weapons policy
Nuclear weapons policy is the set of principles, laws, strategies, and international agreements that govern the development, deployment, potential use, and control of nuclear weapons by states and organizations.
-
B.
nuclear weapons program
A nuclear weapons program is an organized, often state-led effort to research, develop, test, produce, and maintain nuclear warheads and their delivery systems for military deterrence or potential use.
-
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.
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.
-
E.
nuclear weapons crisis
A nuclear weapons crisis is a high-stakes international confrontation in which the use or threatened use of nuclear arms becomes a realistic possibility, creating urgent risks of catastrophic escalation and intense diplomatic, military, and political pressure to resolve the conflict.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:35 p.m.