Triple
T29888304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estação Ecológica |
E759075
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Brazilian protected area category |
C3107
|
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: Brazilian protected area category Context triple: [Estação Ecológica, instanceOf, Brazilian protected area category]
-
A.
Atlantic Forest conservation unit
An Atlantic Forest conservation unit is a legally protected area designated to preserve the biodiversity, ecosystems, and ecological processes of Brazil’s Atlantic Forest biome while regulating human use and promoting sustainable management.
-
B.
network of protected areas
A network of protected areas is a coordinated system of geographically distinct conservation sites managed collectively to maintain biodiversity, ecological processes, and landscape connectivity.
-
C.
sector of Tijuca National Park
A sector of Tijuca National Park is a defined management and geographic subdivision of the park, characterized by specific natural features, conservation objectives, and permitted public uses.
-
D.
type of protected area
chosen
A type of protected area is a designated geographic space, recognized and managed through legal or other effective means, to achieve long-term conservation of nature and associated ecosystem services and cultural values.
-
E.
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.
- 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:01 p.m.