Triple
T25074112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MFO |
E628000
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | peacekeeping organization |
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: peacekeeping organization Context triple: [MFO, instanceOf, peacekeeping organization]
-
A.
peacekeeping support entity
A peacekeeping support entity is an organization or unit that provides logistical, operational, advisory, and humanitarian assistance to facilitate and sustain peacekeeping missions in conflict or post-conflict areas.
-
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.
United Nations peace operations unit
A United Nations peace operations unit is an organized group mandated by the UN to help maintain or restore peace and security in conflict-affected areas through activities such as monitoring ceasefires, protecting civilians, supporting political processes, and facilitating humanitarian assistance.
-
D.
peace enforcement mission
A peace enforcement mission is a military or multinational operation authorized to use coercive measures, including force, to compel compliance with international mandates and restore or maintain peace in a conflict area.
-
E.
peacekeeping support structure
A peacekeeping support structure is an organized framework of logistical, administrative, and operational resources that enables and sustains peacekeeping missions in conflict or post-conflict environments.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:20 a.m.