Triple
T15887838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontiers of the Roman Empire |
E385234
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transnational World Heritage Site |
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: transnational World Heritage Site Context triple: [Frontiers of the Roman Empire, instanceOf, transnational World Heritage Site]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
part of a World Heritage Site
A "part of a World Heritage Site" is a distinct physical or functional component within a designated World Heritage property that contributes to its overall outstanding universal value.
-
E.
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.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:51 a.m.