Triple
T22989441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Six-Party Talks |
E572005
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear disarmament negotiation |
C22995
|
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 disarmament negotiation Context triple: [Six-Party Talks, instanceOf, nuclear disarmament negotiation]
-
A.
disarmament body
chosen
A disarmament body is an organization or institutional entity responsible for negotiating, implementing, monitoring, or promoting the reduction, limitation, or elimination of weapons, particularly weapons of mass destruction.
-
B.
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.
-
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.
nuclear weapons crisis
A nuclear weapons crisis is a high-stakes international confrontation in which the use or threatened use of nuclear arms becomes a realistic possibility, creating urgent risks of catastrophic escalation and intense diplomatic, military, and political pressure to resolve the conflict.
-
E.
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.
- 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:49 p.m.