Triple
T15944071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage documentation |
E386640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNESCO program output |
C36719
|
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 program output Context triple: [UNESCO World Heritage documentation, instanceOf, UNESCO program output]
-
A.
UNESCO programme
A UNESCO programme is an organized, often multi-year initiative led or coordinated by UNESCO to advance its mandate in education, science, culture, communication, or heritage through specific projects, partnerships, and policies.
-
B.
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.
-
C.
UNESCO campaign
A UNESCO campaign is a coordinated global initiative led or endorsed by UNESCO to promote awareness, advocacy, and action around education, science, culture, or communication-related issues in line with its mandate.
-
D.
UNESCO policy document
A UNESCO policy document is an official written instrument that articulates UNESCO’s principles, standards, and recommended actions to guide member states and stakeholders in specific areas of education, science, culture, or communication.
-
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. 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:53 a.m.