Triple
T2406687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuclear Non-Proliferation Act of 1978 |
E50291
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear nonproliferation legislation |
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 nonproliferation legislation Context triple: [Nuclear Non-Proliferation Act of 1978, instanceOf, nuclear nonproliferation legislation]
-
A.
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.
-
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-free policy
A nuclear-free policy is a governmental or organizational commitment to prohibit the development, possession, deployment, or use of nuclear weapons (and often nuclear power) within a defined jurisdiction or scope.
-
D.
nuclear weapons proposal
A nuclear weapons proposal is a formal plan or document outlining the development, acquisition, deployment, or modification of nuclear armaments, including their strategic rationale, technical specifications, and anticipated impacts.
-
E.
nuclear reservation
A nuclear reservation is a designated area of land set aside for the development, testing, production, storage, or decommissioning of nuclear materials and facilities under strict regulatory control.
- 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_69a88b0339a88190a1207333cd271cc9 |
completed | March 4, 2026, 7:41 p.m. |
Created at: March 4, 2026, 7:58 p.m.