Triple
T18925149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bureau for Policy and Programme Support (UNDP) |
E462954
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | policy and programme support entity |
C40022
|
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: policy and programme support entity Context triple: [Bureau for Policy and Programme Support (UNDP), instanceOf, policy and programme support entity]
-
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.
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.
-
C.
sectoral policy organ
A sectoral policy organ is an institutional body responsible for formulating, coordinating, and overseeing policies within a specific economic or social sector, such as health, education, or agriculture.
-
D.
governance entity
chosen
A governance entity is an individual, group, or organization with the authority and responsibility to establish, oversee, and enforce rules, policies, and decisions within a defined domain.
-
E.
public funding body
A public funding body is a government or publicly mandated organization that allocates financial resources to support projects, institutions, or activities in line with public policy goals and societal needs.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:59 a.m.