Triple
T38333600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 2 (Hong Kong) |
E1037890
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic highway 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: strategic highway corridor Context triple: [Route 2 (Hong Kong), instanceOf, strategic highway 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.
transport corridor segment
A transport corridor segment is a defined linear portion of a transportation route (such as a road, rail line, or shipping lane) characterized by consistent physical, operational, and regulatory attributes used for planning, management, and analysis.
-
D.
highway system
A highway system is an interconnected network of major roads and supporting infrastructure designed to enable efficient, high-capacity vehicular travel between cities and regions.
-
E.
highway
A highway is a major public road designed for high-speed, long-distance vehicular travel, typically featuring multiple lanes, limited access points, and safety 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.