Triple
T31428081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biosphärenpark Wienerwald |
E801721
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biosphere reserve in Austria |
C634
|
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: biosphere reserve in Austria Context triple: [Biosphärenpark Wienerwald, instanceOf, biosphere reserve in Austria]
-
A.
UNESCO biosphere reserve
chosen
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.
biosphere reserve candidate area
A biosphere reserve candidate area is a geographically defined region proposed for designation as a biosphere reserve, recognized for its valuable ecosystems and potential to support conservation, sustainable development, and scientific research.
-
C.
protected area in the Alps
A protected area in the Alps is a legally designated mountain region managed to conserve its unique alpine ecosystems, landscapes, and biodiversity while regulating human activities such as tourism, grazing, and development.
-
D.
biosphere region
A biosphere region is a large, distinct area of Earth where living organisms interact with each other and their physical environment, forming an integrated ecological system.
-
E.
region of Austria
A region of Austria is a geographically defined area within the country characterized by shared administrative boundaries, cultural traits, economic activities, and natural features.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 8:55 p.m.