Triple
T23308249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park system plans for New Haven, Connecticut |
E590509
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | city 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: city planning document Context triple: [Park system plans for New Haven, Connecticut, instanceOf, city planning document]
-
A.
citywide planning initiative
A citywide planning initiative is a coordinated, long-term effort by municipal stakeholders to guide land use, infrastructure, services, and development policies across an entire city to achieve shared social, economic, and environmental goals.
-
B.
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.
-
C.
town planning policy
Town planning policy is a set of rules and guidelines that shape how land is used and developed in a town to balance social, economic, and environmental needs.
-
D.
urban planning book
An urban planning book is a comprehensive text that explores the theories, methods, policies, and case studies involved in designing and managing the physical, social, and economic development of cities and urban regions.
-
E.
urban planning structure
An urban planning structure is a designed physical or organizational element within a city—such as streets, parks, zoning frameworks, or transit systems—that shapes how urban space is organized, used, and experienced.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:05 p.m.