Triple
T36714284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nunn–Lugar Cooperative Threat Reduction Program |
E906874
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nonproliferation program |
C44102
|
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: nonproliferation program Context triple: [Nunn–Lugar Cooperative Threat Reduction Program, instanceOf, nonproliferation program]
-
A.
nonproliferation research center
A nonproliferation research center is an institution dedicated to studying, analyzing, and developing policies and technologies to prevent the spread of nuclear, chemical, biological, and other weapons of mass destruction.
-
B.
non-proliferation mechanism
chosen
A non-proliferation mechanism is a policy, agreement, technology, or institutional arrangement designed to prevent or limit the spread of weapons, sensitive materials, or related technologies to unauthorized states or actors.
-
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.
arms control program
An arms control program is an organized set of policies, agreements, and verification measures designed to limit, reduce, or regulate the development, stockpiling, and use of weapons to enhance security and stability.
-
E.
nuclear policy research program
A nuclear policy research program systematically studies and evaluates nuclear weapons, energy, and nonproliferation issues to inform evidence-based national and international policy decisions.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.