Triple
T30740271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNDP Human Development Report Office |
E782673
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research and policy unit |
C5451
|
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: research and policy unit Context triple: [UNDP Human Development Report Office, instanceOf, research and policy unit]
-
A.
research and collaboration unit
A research and collaboration unit is an organizational entity that coordinates and conducts systematic inquiry while facilitating partnerships and knowledge exchange among internal and external stakeholders.
-
B.
policy analysis unit
chosen
A policy analysis unit is an organizational entity responsible for systematically evaluating, comparing, and forecasting the impacts of public or institutional policies to inform evidence-based decision-making.
-
C.
public policy research institute
A public policy research institute is an organization that conducts independent, systematic analysis of public issues to inform and influence government decision-making and public debate.
-
D.
research and engagement centre
A research and engagement centre is an institution that conducts systematic inquiry into specific fields while actively collaborating with and involving stakeholders or communities to apply, share, and co-create knowledge.
-
E.
research and competence centre
A research and competence centre is an organizational unit that conducts advanced studies and develops, concentrates, and disseminates specialized expertise within a particular field to support innovation, education, and practical application.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:37 p.m.