Triple
T37275714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston–San Antonio |
E924640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intercity 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: intercity corridor Context triple: [Houston–San Antonio, instanceOf, intercity corridor]
-
A.
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.
-
B.
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.
-
C.
suburban railway corridor
A suburban railway corridor is a dedicated rail route connecting city centers with surrounding residential suburbs, designed to support frequent, high-capacity commuter train services.
-
D.
intercity coach network
An intercity coach network is a coordinated system of long-distance bus routes, schedules, vehicles, and terminals that connects multiple cities to provide affordable, scheduled passenger transport.
-
E.
planned transit corridor
A planned transit corridor is a designated route or area reserved for future development of public transportation infrastructure, such as bus rapid transit or rail lines, to guide growth and improve regional mobility.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.