Triple
T19966032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ragusa |
E479934
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNESCO World Heritage City |
C28743
|
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 City Context triple: [Ragusa, instanceOf, UNESCO World Heritage City]
-
A.
former UNESCO World Heritage Site
A former UNESCO World Heritage Site is a location that was once inscribed on the World Heritage List for its outstanding universal value but has since been removed due to loss of integrity, authenticity, or failure to meet UNESCO’s preservation standards.
-
B.
UNESCO distinction
A UNESCO distinction is an official recognition or designation granted by UNESCO to sites, practices, or entities that exemplify outstanding cultural, natural, educational, or scientific value in line with its global mission.
-
C.
World Heritage site
chosen
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.
-
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 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.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:54 p.m.