Triple
T31662047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Heritage Cities Programme |
E808027
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World Heritage Centre programme |
C2058
|
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: World Heritage Centre programme Context triple: [World Heritage Cities Programme, instanceOf, World Heritage Centre programme]
-
A.
World Heritage Centre
The World Heritage Centre is an organization or entity responsible for identifying, protecting, and managing cultural and natural sites of outstanding universal value around the globe.
-
B.
UNESCO programme
chosen
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.
heritage conservation programme
A heritage conservation programme is an organized set of policies, actions, and resources aimed at identifying, protecting, and sustainably managing cultural and natural heritage for present and future generations.
-
D.
cultural heritage organisation
A cultural heritage organisation is an institution dedicated to preserving, managing, and promoting tangible and intangible cultural assets—such as artifacts, traditions, sites, and knowledge—for the benefit of present and future generations.
-
E.
cultural heritage programme
A cultural heritage programme is an organized set of initiatives designed to identify, preserve, promote, and transmit a community’s tangible and intangible cultural assets across generations.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:57 p.m.