Triple
T29843588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Comprehensive Waterfront Plan |
E757867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal planning document |
C29334
|
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: municipal planning document Context triple: [New York City Comprehensive Waterfront Plan, instanceOf, municipal planning document]
-
A.
municipal policy framework
A municipal policy framework is a structured set of principles, regulations, and procedures that guide a city or local government's decision-making, service delivery, and long-term planning.
-
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.
municipal policy
Municipal policy is a set of rules, regulations, and strategic decisions adopted by a local government to guide the planning, management, and delivery of public services and community development within its jurisdiction.
-
D.
urban planning master plan
chosen
An urban planning master plan is a comprehensive, long-term framework that guides the physical, social, and economic development of a city or region through coordinated land use, infrastructure, and policy strategies.
-
E.
planning district
A planning district is a defined geographic area used by governments or organizations to coordinate land use, infrastructure, and development policies.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:40 p.m.