Triple
T18713400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage Site component |
E457574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage designation element |
C827
|
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 designation element Context triple: [UNESCO World Heritage Site component, instanceOf, heritage designation element]
-
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.
cultural heritage designation
chosen
A cultural heritage designation is an official recognition granted by an authority to protect and preserve places, objects, or practices of significant historical, cultural, or artistic value.
-
C.
cultural heritage element
A cultural heritage element is a tangible or intangible manifestation of a community’s traditions, practices, expressions, knowledge, or artifacts that is valued, preserved, and transmitted across generations.
-
D.
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.
-
E.
historic designation
A historic designation is an official recognition granted to a place, structure, or object for its significant historical, architectural, cultural, or archaeological value, often providing it with legal protections and conservation guidelines.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.