Triple
T30015767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Streets corridor (nearby South Capitol/MLK corridors) |
E762590
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | streetscape improvement area |
C56641
|
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: streetscape improvement area Context triple: [Great Streets corridor (nearby South Capitol/MLK corridors), instanceOf, streetscape improvement area]
-
A.
streetscape setting
A streetscape setting is the visual and functional arrangement of elements along a street—such as buildings, sidewalks, trees, lighting, and street furniture—that together shape the character and experience of the public realm.
-
B.
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.
-
C.
street
A street is a public thoroughfare in an urban or suburban area, typically bordered by buildings, that facilitates vehicular and pedestrian movement and often supports various social and commercial activities.
-
D.
civic thoroughfare
A civic thoroughfare is a major public street or corridor designed to accommodate high volumes of movement while structuring and showcasing key civic, cultural, and institutional functions of a community.
-
E.
neighborhood corridor
A neighborhood corridor is a linear, mixed-use area within a community that concentrates housing, shops, services, and transportation along a primary street to support walkability and local activity.
- F. None of above. chosen
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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:45 p.m.