Triple
T5801531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humanitarian Coordination Liaison |
E128632
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | position in UN peace operations |
C14270
|
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: position in UN peace operations Context triple: [Humanitarian Coordination Liaison, instanceOf, position in UN peace operations]
-
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.
senior United Nations position
chosen
A senior United Nations position is a high-level leadership role responsible for shaping and implementing UN policies, strategies, and operations across member states and agencies.
-
C.
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.
-
D.
peacekeeping force
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.
-
E.
United Nations role
The "United Nations role" conceptual class represents the specific function, responsibility, or position an entity holds within the UN system, such as mediator, peacekeeper, observer, or member state.
- 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.