Triple
T6712156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Avenue commercial corridor |
E153170
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban commercial corridor |
C526
|
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: urban commercial corridor Context triple: [Massachusetts Avenue commercial corridor, instanceOf, urban commercial corridor]
-
A.
urban business district
chosen
An urban business district is a densely developed area within a city characterized by a high concentration of offices, commercial activities, financial institutions, and supporting services that form the economic core of the urban environment.
-
B.
urban beltway
An urban beltway is a high-capacity circumferential highway or roadway system that encircles a city to route traffic around its core, reduce congestion, and connect radial routes and suburbs.
-
C.
urban promenade
An urban promenade is a designed public walkway or boulevard in a city, intended for leisurely strolling, social interaction, and visual enjoyment of the surrounding urban landscape.
-
D.
urban plaza
An urban plaza is a publicly accessible open space within a city, typically surrounded by buildings and streets, designed to support social interaction, circulation, and civic activities.
-
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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:07 p.m.