Triple
T4654647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO/CEPES |
E102379
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNESCO regional centre |
C17318
|
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: UNESCO regional centre Context triple: [UNESCO/CEPES, instanceOf, UNESCO regional centre]
-
A.
UNESCO regional committee
A UNESCO regional committee is a governance body that coordinates, advises, and implements UNESCO’s programs and policies within a specific geographic region, facilitating cooperation among member states and regional partners.
-
B.
UNESCO regional group
A UNESCO regional group is a coalition of member states organized by geographic and political regions within UNESCO to coordinate positions, representation, and decision-making in the organization’s activities and governance.
-
C.
UNESCO section
A UNESCO section is an organizational unit within UNESCO responsible for managing specific thematic areas, programs, or functions in support of the organization’s educational, scientific, and cultural mission.
-
D.
UNESCO advisory body
A UNESCO advisory body is an expert committee or organization that provides specialized guidance, evaluations, and recommendations to UNESCO to inform its decisions, policies, and program implementation in specific fields such as culture, education, science, or heritage.
-
E.
UNESCO fund
A UNESCO fund is a financial mechanism established by the United Nations Educational, Scientific and Cultural Organization to support projects and programs that advance education, science, culture, and communication worldwide.
- F. None of above. chosen
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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:14 p.m.