Triple
T31024518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO Havana Office |
E790531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNESCO field office |
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 field office Context triple: [UNESCO Havana Office, instanceOf, UNESCO field office]
-
A.
UNESCO constituency
A UNESCO constituency is a group of member states or stakeholders collectively represented within UNESCO’s governance structures to coordinate positions, share interests, and influence the organization’s policies and programs.
-
B.
UNESCO institute
A UNESCO institute is a specialized organizational unit established by UNESCO to advance its mission through focused research, education, capacity-building, and policy support in specific fields such as culture, science, education, or communication.
-
C.
UNESCO regional centre
chosen
A UNESCO regional centre is an institution established under the auspices of UNESCO to support and coordinate specialized educational, scientific, or cultural activities across a specific geographic region.
-
D.
UNESCO official
A UNESCO official is a representative or staff member of the United Nations Educational, Scientific and Cultural Organization responsible for developing, coordinating, and implementing programs and policies in education, science, culture, and communication worldwide.
-
E.
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.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:58 p.m.