Triple
T26503044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco Bay Area open space network |
E669470
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional open space system |
C13459
|
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 system Context triple: [San Francisco Bay Area open space network, instanceOf, regional open space system]
-
A.
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.
-
B.
urban park system component
An urban park system component is an individual physical or programmatic element—such as a park, trail, plaza, facility, or natural feature—that collectively contributes to the recreational, ecological, and social functions of a city’s interconnected green space network.
-
C.
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.
-
D.
open space park
An open space park is a large, predominantly undeveloped public area preserved for recreation, natural habitat, and scenic enjoyment.
-
E.
public open space system
chosen
A public open space system is an interconnected network of accessible parks, plazas, greenways, and natural areas designed to support recreation, social interaction, ecological health, and urban livability for all community members.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:14 a.m.