Triple
T36714283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nunn–Lugar Cooperative Threat Reduction Program |
E906874
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | arms control program |
C64372
|
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 program Context triple: [Nunn–Lugar Cooperative Threat Reduction Program, instanceOf, arms control program]
-
A.
arms control regime
An arms control regime is a set of formal and informal agreements, institutions, and practices through which states collectively regulate the development, possession, and use of weapons to enhance security and stability.
-
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.
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.
-
D.
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.
-
E.
missile defense program
A missile defense program is an organized system of technologies, policies, and operations designed to detect, track, intercept, and neutralize incoming missiles before they reach their intended targets.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.