Triple
T26344807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO natural criteria |
E662752
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage evaluation framework |
C47508
|
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: heritage evaluation framework Context triple: [UNESCO natural criteria, instanceOf, heritage evaluation framework]
-
A.
heritage protection system element
A heritage protection system element is a component—such as a policy, structure, technology, or procedure—designed to prevent damage, loss, or degradation of cultural or natural heritage assets.
-
B.
heritage inventory program
chosen
A heritage inventory program is a systematic initiative to identify, document, and evaluate cultural, historical, and natural heritage resources within a defined area for their protection, management, and public awareness.
-
C.
heritage asset
A heritage asset is a building, monument, site, landscape, or object of historical, cultural, architectural, or archaeological significance that is preserved for its value to present and future generations.
-
D.
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.
-
E.
cultural heritage protection system
A cultural heritage protection system is an integrated framework of policies, technologies, and practices designed to identify, preserve, monitor, and safeguard tangible and intangible cultural assets from damage, loss, or unauthorized exploitation.
- 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.