Triple
T1289211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Heritage Committee |
E27506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNESCO body |
C4250
|
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 body Context triple: [World Heritage Committee, instanceOf, UNESCO body]
-
A.
principal organ of UNESCO
chosen
The principal organ of UNESCO is a primary governing body responsible for setting the organization’s policies, strategic direction, and overall programmatic priorities.
-
B.
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.
-
C.
UNESCO convention
A UNESCO convention is a formal international treaty adopted by UNESCO member states to establish legally binding standards and cooperative frameworks for protecting and promoting cultural, natural, educational, or intangible heritage worldwide.
-
D.
UNESCO recommendation
A UNESCO recommendation is a non-binding normative instrument adopted by UNESCO’s General Conference that provides guidance and standards for member states on specific educational, scientific, cultural, or communication issues.
-
E.
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.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
Created at: March 1, 2026, 7:51 p.m.