Triple
T26344806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO natural criteria |
E662752
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World Heritage selection criteria |
C8771
|
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 selection criteria Context triple: [UNESCO natural criteria, instanceOf, World Heritage selection criteria]
-
A.
World Heritage site
A World Heritage site is a landmark or area recognized by UNESCO as having outstanding universal value to humanity for its cultural, natural, or mixed significance, warranting protection and preservation for future generations.
-
B.
component of World Heritage Convention framework
chosen
A component of the World Heritage Convention framework is an element—such as a principle, process, body, or instrument—that collectively contributes to identifying, protecting, conserving, presenting, and transmitting World Heritage properties to future generations.
-
C.
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.
-
D.
UNESCO register
A UNESCO register is an official list maintained by UNESCO that records and recognizes sites, practices, or items of outstanding cultural or natural significance for protection and preservation.
-
E.
UNESCO World Heritage Site list by country
A UNESCO World Heritage Site list by country is an organized catalog that groups and details all UNESCO-designated cultural and natural heritage sites within each individual nation.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:41 p.m.