Triple
T33085743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Cruz Mountains regional open space network |
E846634
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional open space network |
C15458
|
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: regional open space network Context triple: [Santa Cruz Mountains regional open space network, instanceOf, regional open space network]
-
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.
network of protected areas
chosen
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.
coastal open space
A coastal open space is a natural or minimally developed shoreline area that provides public access, recreation, and ecological protection along the coast.
-
D.
regional collaborative network
A regional collaborative network is a structured alliance of organizations, institutions, and stakeholders within a specific geographic area that coordinate resources, knowledge, and activities to address shared goals and regional challenges.
-
E.
local and regional planning framework
A local and regional planning framework is a structured set of policies, processes, and tools that guide coordinated land use, infrastructure, and development decisions across municipalities and regions to achieve sustainable, equitable, and efficient growth.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:26 a.m.