Triple
T11557869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mediation Support Unit |
E274060
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mediation support entity |
C18889
|
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: mediation support entity Context triple: [Mediation Support Unit, instanceOf, mediation support entity]
-
A.
mediation support function
chosen
A mediation support function is a structured capability or service that provides tools, processes, and expertise to help design, facilitate, and manage mediation activities between disputing parties.
-
B.
mediation group
A mediation group is a structured assembly of neutral facilitators and disputing parties who collaboratively work to resolve conflicts through guided communication and negotiated agreement.
-
C.
labor mediator
A labor mediator is a neutral third party who facilitates communication and negotiation between employers and employees (or their representatives) to help resolve workplace or collective bargaining disputes without resorting to litigation or strikes.
-
D.
peacebuilding support entity
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.
-
E.
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.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:37 p.m.