Triple
T3835823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erzgebirge/Krušnohoří Mining Region |
E91129
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transboundary protected area |
C7343
|
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: transboundary protected area Context triple: [Erzgebirge/Krušnohoří Mining Region, instanceOf, transboundary protected area]
-
A.
transboundary region
A transboundary region is a geographically contiguous area that spans across the borders of two or more political or administrative jurisdictions, sharing interconnected environmental, economic, social, or cultural systems.
-
B.
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.
-
C.
protected area designation in the United States
A protected area designation in the United States is an official legal or administrative status applied to lands and waters to conserve natural, cultural, or recreational resources by regulating their use and development.
-
D.
cross-border area
chosen
A cross-border area is a geographic region that spans across the boundaries of two or more countries, where social, economic, environmental, and political interactions occur and are often managed through cooperative arrangements.
-
E.
nature reserve
A nature reserve is a protected area of land or water designated to conserve wildlife, habitats, and natural features, often limiting human activities to research, education, and low-impact recreation.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.