Triple
T33785426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zona Reservada Santiago–Comaina |
E865772
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former protected natural area |
C15515
|
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: former protected natural area Context triple: [Zona Reservada Santiago–Comaina, instanceOf, former protected natural area]
-
A.
former protected area designation
chosen
A former protected area designation is a status previously assigned to a geographic region to recognize and regulate its conservation value, which has since been revoked, replaced, or otherwise discontinued.
-
B.
Protected natural area
A protected natural area is a geographically defined space designated and managed to conserve biodiversity, natural resources, and ecosystem services while limiting or regulating human activities.
-
C.
former state park
A former state park is a protected natural or recreational area that was once officially designated and managed as a state park but has since been reclassified, transferred, or decommissioned from that status.
-
D.
protected natural area system
A protected natural area system is an organized network of geographically defined spaces managed through legal or other effective means to conserve biodiversity, ecosystem services, and natural or cultural values over the long term.
-
E.
protected landscape area
A protected landscape area is a designated region where the interaction of people and nature over time has produced a distinct character with significant ecological, cultural, and scenic value that is conserved and managed through legal or other effective means.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.