Triple
T33716556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenida Juárez corridor |
E863889
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street corridor |
C1088
|
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: street corridor Context triple: [Avenida Juárez corridor, instanceOf, street corridor]
-
A.
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.
-
B.
street
chosen
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.
-
C.
institutional corridor
An institutional corridor is a long, functional passageway within a formal facility (such as a school, hospital, or government building) that connects rooms and departments while regulating movement and access.
-
D.
streetcar corridor
A streetcar corridor is a designated urban transit route where streetcars operate along fixed tracks, typically integrated into city streets, to provide frequent, high-capacity public transportation and support adjacent mixed-use development.
-
E.
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.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:44 a.m.