Triple
T29443111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | highways connecting to Al-Qassim |
E746771
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road transport infrastructure network |
C4130
|
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 transport infrastructure network Context triple: [highways connecting to Al-Qassim, instanceOf, road transport infrastructure network]
-
A.
transport infrastructure network
chosen
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.
-
B.
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.
-
C.
road infrastructure
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.
-
D.
road transport node
A road transport node is a specific location within a road network where vehicles and travelers converge, diverge, or transfer, such as intersections, terminals, or hubs.
-
E.
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.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:24 p.m.