Triple
T741359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuclear Planning Group |
E15250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear policy coordination body |
C172
|
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 policy coordination body Context triple: [Nuclear Planning Group, instanceOf, nuclear policy coordination body]
-
A.
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.
-
B.
federation of government agencies
A federation of government agencies is a collaborative structure in which multiple semi-autonomous public organizations coordinate policies, resources, and operations to achieve shared governmental objectives while retaining their individual mandates.
-
C.
counterproliferation organization
A counterproliferation organization is an entity dedicated to preventing, detecting, and responding to the development, acquisition, and spread of weapons of mass destruction and related delivery systems.
-
D.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
E.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.