Triple
T538989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Security Council Resolution 687 |
E12387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disarmament measure |
C3337
|
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: disarmament measure Context triple: [UN Security Council Resolution 687, instanceOf, disarmament measure]
-
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.
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.
-
C.
anti-nuclear weapons document
chosen
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.
-
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.
appeasement policy milestone
An appeasement policy milestone is a significant historical or political event in which concessions are made to a potentially hostile power in hopes of maintaining peace or avoiding conflict.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:32 p.m.