Triple
T2513472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tremont Street commercial corridor |
E52753
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mixed-use corridor |
C727
|
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: mixed-use corridor Context triple: [Tremont Street commercial corridor, instanceOf, mixed-use corridor]
-
A.
mixed-use development district
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.
-
B.
mixed-use lifestyle center
chosen
A mixed-use lifestyle center is a planned development that combines retail, dining, entertainment, residential, and often office spaces in a walkable, open-air environment designed to create a vibrant, community-oriented destination.
-
C.
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.
-
D.
population corridor
A population corridor is a geographic or infrastructural pathway that facilitates the movement, interaction, and distribution of people between distinct population centers.
-
E.
transport corridor
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
- 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:46 p.m.