Triple
T38506574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyde Park road network |
E921781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban circulation system |
C44796
|
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 circulation system Context triple: [Hyde Park road network, instanceOf, urban circulation system]
-
A.
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.
-
B.
urban retail corridor system
An urban retail corridor system is a network of interconnected commercial streets, storefronts, public spaces, and supporting infrastructure that collectively organize, concentrate, and facilitate pedestrian-oriented shopping, services, and social activity within a city.
-
C.
urban system
chosen
An urban system is an interconnected network of cities and their surrounding regions, encompassing the flows of people, goods, information, and resources that shape their social, economic, and environmental dynamics.
-
D.
urban arterial road
An urban arterial road is a high-capacity city street designed to carry large volumes of traffic efficiently between local streets and major highways while providing controlled access to adjacent land uses.
-
E.
urban junction
An urban junction is a point where multiple city streets or transportation routes intersect, facilitating the flow and regulation of vehicular, pedestrian, and sometimes transit traffic within an urban network.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:32 p.m.