Triple
T967265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MONUSCO |
E20864
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | stabilization mission |
C1802
|
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: stabilization mission Context triple: [MONUSCO, instanceOf, stabilization mission]
-
A.
United Nations peacekeeping mission
A United Nations peacekeeping mission is an international operation authorized by the UN to help maintain or restore peace and security in conflict-affected areas through the deployment of military, police, and civilian personnel under impartial mandates.
-
B.
peacekeeping force
chosen
A peacekeeping force is an organized, often multinational group deployed to conflict or post-conflict areas to monitor ceasefires, support political processes, protect civilians, and help maintain or restore peace and security.
-
C.
military operation
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
D.
multinational mission mechanism
A multinational mission mechanism is a structured framework of processes, agreements, and coordinating bodies that enables multiple countries or organizations to collaboratively plan, resource, and execute a shared mission across borders.
-
E.
mission to the United Nations
A mission to the United Nations is a permanent diplomatic representation of a member state or observer entity to the UN, responsible for managing its participation, negotiations, and interests within the organization.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:40 p.m.