Triple
T11603082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley Road area |
E275181
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traffic corridor |
C2952
|
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: traffic corridor Context triple: [Valley Road area, instanceOf, traffic corridor]
-
A.
road transportation corridor
A road transportation corridor is a designated linear area of land that accommodates one or more roadways and associated infrastructure to enable the efficient movement of vehicles, goods, and people between key origins and destinations.
-
B.
transport corridor
chosen
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.
-
C.
population corridor
A population corridor is a geographic or infrastructural pathway that facilitates the movement, interaction, and distribution of people between distinct population centers.
-
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.
arterial roadway
An arterial roadway is a high-capacity urban or suburban street designed to efficiently carry large volumes of through traffic between local streets and highways while providing limited direct property access.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:38 p.m.