Triple
T25516759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston (via Lake Shore Limited) |
E639527
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | passenger rail terminus |
C25472
|
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: passenger rail terminus Context triple: [Boston (via Lake Shore Limited), instanceOf, passenger rail terminus]
-
A.
passenger rail terminal
chosen
A passenger rail terminal is a dedicated facility where travelers board, disembark, and transfer between trains, supported by platforms, ticketing, waiting areas, and related passenger services.
-
B.
group of passenger rail terminals
A group of passenger rail terminals is a collection of interconnected or related railway stations designed for boarding, alighting, and transferring passengers within a coordinated transport network.
-
C.
commuter rail station
A commuter rail station is a designated facility where passengers board and alight regional trains that connect suburbs or outlying areas with urban centers, typically offering platforms, ticketing, and basic passenger amenities.
-
D.
railway bridge terminus
A railway bridge terminus is the endpoint of a rail line where tracks transition from or onto a bridge structure, often incorporating platforms, signaling, and facilities for train arrival, departure, and turnaround.
-
E.
airport rail station
An airport rail station is a transportation facility that directly connects an airport to regional or long-distance rail networks, enabling passengers to transfer efficiently between air and train travel.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:56 p.m.