Triple
T23308251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park system plans for New Haven, Connecticut |
E590509
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic planning scheme |
C36009
|
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: historic planning scheme Context triple: [Park system plans for New Haven, Connecticut, instanceOf, historic planning scheme]
-
A.
historic district plan
A historic district plan is a comprehensive guiding document that outlines policies, design standards, and preservation strategies to protect and enhance the cultural, architectural, and historical character of a designated area.
-
B.
historic urban layout
A historic urban layout is the enduring spatial arrangement of streets, plots, public spaces, and building patterns that reflects the social, economic, and cultural organization of a city in a past period.
-
C.
heritage site development plan
chosen
A heritage site development plan is a strategic framework that guides the conservation, use, and enhancement of a heritage site while balancing cultural significance, visitor experience, community needs, and sustainable development.
-
D.
historic establishment
A historic establishment is a long-standing place of business or institution recognized for its significant role, continuity, and influence in a particular community or period of history.
-
E.
landmark planning blueprint
A landmark planning blueprint is a strategic, visual, and documented plan that outlines the design, placement, significance, and long-term development of key landmarks within a geographic or urban context.
- 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.