Triple
T14570571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd Ring Road (Beijing) |
E341899
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road infrastructure in Beijing |
C2978
|
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: road infrastructure in Beijing Context triple: [2nd Ring Road (Beijing), instanceOf, road infrastructure in Beijing]
-
A.
road infrastructure
chosen
Road infrastructure encompasses the physical structures, systems, and facilities—such as roads, bridges, tunnels, signage, and drainage—designed and built to support safe and efficient vehicular and pedestrian transportation.
-
B.
road in Shanghai
A road in Shanghai is a transportation corridor within the city’s dense urban fabric that supports mixed traffic—vehicles, buses, bicycles, and pedestrians—while integrating local infrastructure, commercial activity, and municipal regulations specific to Shanghai.
-
C.
road network
A road network is an interconnected system of roads, intersections, and related infrastructure that enables the movement of vehicles and pedestrians between different locations.
-
D.
transport infrastructure network
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
E.
road in Berlin
A road in Berlin is a public thoroughfare within the city’s urban network that facilitates vehicular, bicycle, and pedestrian movement while integrating with Berlin’s historical layout, public transit, and zoning infrastructure.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:23 a.m.