Triple
T20205519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard Allston expansion area |
E493339
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | development district |
C726
|
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: development district Context triple: [Harvard Allston expansion area, instanceOf, development district]
-
A.
planning district
A planning district is a defined geographic area used by governments or organizations to coordinate land use, infrastructure, and development policies.
-
B.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
-
C.
development authority
A development authority is an organization or governmental body responsible for planning, regulating, and facilitating land use, infrastructure, and urban or regional development within a designated area.
-
D.
mixed-use development district
chosen
A mixed-use development district is a designated urban area that intentionally combines residential, commercial, recreational, and sometimes industrial uses within a walkable, integrated environment to promote vibrant, efficient, and sustainable community life.
-
E.
development corridor
A development corridor is a strategically planned geographic area, often aligned along major transportation routes, where concentrated investment in infrastructure, industry, and services is used to stimulate economic growth and regional integration.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:38 p.m.