Triple
T20801404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuclear-weapon-free zones |
E512047
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | arms control regime |
C44103
|
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: arms control regime Context triple: [Nuclear-weapon-free zones, instanceOf, arms control regime]
-
A.
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.
-
B.
arms control advocate
An arms control advocate is an individual who actively promotes the limitation, reduction, and responsible regulation of weapons and military capabilities to enhance global security and prevent conflict.
-
C.
arms limitation conference
An arms limitation conference is a formal international meeting where representatives of states negotiate agreements to restrict, reduce, or regulate the development, stockpiling, and deployment of weapons.
-
D.
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.
-
E.
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.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:39 p.m.