Triple
T3710417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Heritage Sites in Poland |
E81397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNESCO World Heritage listing |
C8475
|
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 World Heritage listing Context triple: [World Heritage Sites in Poland, instanceOf, UNESCO World Heritage listing]
-
A.
UNESCO World Heritage region
A UNESCO World Heritage region is a geographically defined area recognized by UNESCO for its outstanding universal value to humanity, encompassing natural, cultural, or mixed heritage that is legally protected and managed for long-term conservation.
-
B.
UNESCO World Heritage Tentative List site
chosen
A UNESCO World Heritage Tentative List site is a cultural or natural property that a country has formally proposed as a candidate for future inscription on the UNESCO World Heritage List.
-
C.
cultural heritage designation
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.
-
D.
national heritage site
A national heritage site is a location, structure, or landscape officially designated by a country as having significant historical, cultural, architectural, or natural value warranting legal protection and preservation.
-
E.
UNESCO biosphere reserve
A UNESCO biosphere reserve is a designated area that promotes solutions reconciling the conservation of biodiversity with its sustainable use, integrating protected ecosystems, research, and local community development.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:33 p.m.