Triple
T29797128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington, D.C.–Richmond, Virginia |
E756584
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rail corridor segment |
C1439
|
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: rail corridor segment Context triple: [Washington, D.C.–Richmond, Virginia, instanceOf, rail corridor segment]
-
A.
freight rail corridor
A freight rail corridor is a designated railway route primarily used for the efficient, high-capacity movement of goods and cargo between industrial, commercial, and logistics hubs.
-
B.
underground rail corridor
An underground rail corridor is a subsurface passageway engineered to safely guide trains between stations, housing tracks, utilities, and supporting infrastructure while minimizing surface disruption.
-
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.
railway line
A railway line is a fixed transportation route consisting of tracks, signaling, and related infrastructure along which trains operate between defined locations.
-
E.
railroad line
chosen
A railroad line is a fixed route consisting of tracks and associated infrastructure over which trains operate to transport passengers or freight between locations.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:16 p.m.