Triple
T35308033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia River wildlife corridor |
E1019690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | habitat connectivity area |
C11502
|
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: habitat connectivity area Context triple: [Columbia River wildlife corridor, instanceOf, habitat connectivity area]
-
A.
habitat network
A habitat network is an interconnected system of natural areas and corridors that facilitates the movement, survival, and genetic exchange of species across a landscape.
-
B.
habitat area
A habitat area is a defined geographic space that provides the necessary environmental conditions and resources to support the life processes of particular species or ecological communities.
-
C.
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.
-
D.
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.
-
E.
ecological corridor
chosen
An ecological corridor is a natural or restored habitat pathway that connects separate wildlife populations, enabling species movement, gene flow, and ecosystem resilience across fragmented landscapes.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.