Triple
T23317245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amtrak stations in Virginia |
E590742
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collection of transport infrastructure |
C2489
|
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: collection of transport infrastructure Context triple: [Amtrak stations in Virginia, instanceOf, collection of transport infrastructure]
-
A.
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.
-
B.
transportation corridors collection
A transportation corridors collection is an organized set of linear pathways—such as roads, railways, and transit routes—grouped for managing, analyzing, or planning movement across a region.
-
C.
public transportation infrastructure
chosen
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
-
D.
transport infrastructure name
A transport infrastructure name identifies a specific facility or network element used for the movement of people or goods, such as a road, railway line, airport, or port.
-
E.
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.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:06 p.m.