Triple
T7177964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interim Agreement on Offensive Arms |
E167367
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear arms limitation agreement |
C8219
|
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 arms limitation agreement Context triple: [Interim Agreement on Offensive Arms, instanceOf, nuclear arms limitation agreement]
-
A.
non‑aggression pact
A non-aggression pact is a formal agreement between two or more parties in which they commit not to engage in military or hostile actions against each other, typically for a specified period.
-
B.
regional arms control norm
A regional arms control norm is a shared expectation among states within a specific geographic area that guides and constrains their behavior regarding the development, deployment, and transfer of weapons to enhance stability and reduce the risk of conflict.
-
C.
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.
-
D.
nuclear weapons policy
chosen
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.
-
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.
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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:49 p.m.