Triple
T7333920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baruch Plan for international control of atomic energy |
E169076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | arms control proposal |
C1586
|
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 proposal Context triple: [Baruch Plan for international control of atomic energy, instanceOf, arms control proposal]
-
A.
nuclear weapons proposal
chosen
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.
-
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 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.
-
D.
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.
-
E.
anti-nuclear weapons document
An anti-nuclear weapons document is a written work that argues against the development, possession, or use of nuclear weapons, often advocating for disarmament, non-proliferation, and alternative security measures.
- 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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:04 p.m.