Triple
T38003795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado transportation planning framework |
E948175
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | statewide planning system |
C21902
|
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: statewide planning system Context triple: [Colorado transportation planning framework, instanceOf, statewide planning system]
-
A.
regional planning program
A regional planning program is an organized framework of policies, strategies, and actions designed to guide the coordinated development, land use, infrastructure, and resource management of a specific geographic area over time.
-
B.
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.
-
C.
statewide initiative
chosen
A statewide initiative is a coordinated program or campaign implemented across an entire state to address a specific policy, social, economic, or public service goal.
-
D.
statewide school system
A statewide school system is a coordinated network of public educational institutions, policies, and administrative bodies that operate under a unified state authority to provide standardized education across all regions within the state.
-
E.
regional planning region
A regional planning region is a geographically defined area used by governments and organizations to coordinate land use, infrastructure, economic development, and environmental policies across multiple local jurisdictions.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.