Triple
T2850541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe and North America |
E63081
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNESCO World Heritage region |
C11137
|
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 region Context triple: [Europe and North America, instanceOf, UNESCO World Heritage region]
-
A.
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.
-
B.
National Heritage Area
A National Heritage Area is a region designated by the U.S. Congress where natural, cultural, and historic resources form a cohesive, nationally important landscape managed through partnerships rather than federal land ownership.
-
C.
State Heritage Area
A State Heritage Area is a geographically defined place recognized and protected by a state government for its outstanding cultural, historical, or natural significance.
-
D.
UNESCO World Heritage Tentative List site
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.
-
E.
component of World Heritage Convention framework
A component of the World Heritage Convention framework is an element—such as a principle, process, body, or instrument—that collectively contributes to identifying, protecting, conserving, presenting, and transmitting World Heritage properties to future generations.
- F. None of above. chosen
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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
Created at: March 6, 2026, 10:02 p.m.