Triple
T5800690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDR Standing Capacity |
E128613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disarmament, demobilization and reintegration support mechanism |
C10379
|
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, demobilization and reintegration support mechanism Context triple: [DDR Standing Capacity, instanceOf, disarmament, demobilization and reintegration support mechanism]
-
A.
chemical demilitarization program office
A chemical demilitarization program office is an organizational entity responsible for planning, managing, and overseeing the safe, compliant destruction of chemical weapons and related materials.
-
B.
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.
-
C.
ceasefire
A ceasefire is a mutually agreed temporary suspension of active hostilities between conflicting parties, typically intended to create conditions for negotiation or humanitarian relief.
-
D.
military withdrawal
Military withdrawal is the planned and coordinated removal of armed forces from an area of operations, often marking the end or repositioning of military engagement.
-
E.
peacebuilding support entity
chosen
A peacebuilding support entity is an organization or mechanism that provides strategic, technical, financial, and coordination assistance to design, implement, and sustain peacebuilding initiatives in conflict-affected or post-conflict contexts.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:52 p.m.