Triple
T28452136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nationally Significant Infrastructure Projects |
E716605
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planning regime category |
C54084
|
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: planning regime category Context triple: [Nationally Significant Infrastructure Projects, instanceOf, planning regime category]
-
A.
planned sector
A planned sector is a designated area within a city or region that is systematically organized and developed according to a comprehensive plan for land use, infrastructure, and services.
-
B.
planning district
A planning district is a defined geographic area used by governments or organizations to coordinate land use, infrastructure, and development policies.
-
C.
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.
-
D.
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.
-
E.
planning commission
A planning commission is a governmental or advisory body responsible for reviewing, guiding, and making recommendations on land use, development proposals, and long-term community planning policies.
- F. None of above. chosen
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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 28, 2026, 1:52 a.m.