Triple
T10477239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cordillera del Cóndor protected zones |
E247076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transboundary conservation area |
C19942
|
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 conservation area Context triple: [Cordillera del Cóndor protected zones, instanceOf, transboundary conservation 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.
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.
binational park
chosen
A binational park is a protected natural or recreational area that spans the border of two countries and is jointly managed or coordinated by both nations.
-
D.
Protected area designation
A protected area designation is an official classification assigned to a geographic region to conserve its natural, cultural, or ecological values by regulating human activities and land use.
-
E.
wildlife dispersal area
A wildlife dispersal area is a designated zone of habitat that facilitates the movement and spread of animal species between core habitats or protected areas, supporting genetic diversity and ecosystem connectivity.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:21 p.m.