Triple
T2770621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Special Commission |
E61446
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disarmament verification commission |
C1218
|
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 verification commission Context triple: [UN Special Commission, instanceOf, disarmament verification commission]
-
A.
armistice supervision body
An armistice supervision body is an organization established to monitor, verify, and enforce compliance with the terms of a ceasefire or armistice agreement between conflicting parties.
-
B.
international monitoring mechanism
chosen
An international monitoring mechanism is a structured system, often established by states or international organizations, that systematically observes, evaluates, and reports on compliance with agreed-upon international norms, laws, or standards across borders.
-
C.
joint commission
A joint commission is a temporary or permanent body formed by representatives from two or more organizations, governments, or parties to collaboratively oversee, regulate, or resolve issues of shared concern.
-
D.
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.
-
E.
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.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:57 p.m.