Triple
T10683873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle Creek Intermodal Transportation Center |
E251825
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intermodal passenger station |
C28624
|
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: intermodal passenger station Context triple: [Battle Creek Intermodal Transportation Center, instanceOf, intermodal passenger station]
-
A.
passenger rail terminal
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.
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.
-
C.
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.
-
D.
rapid transit station
A rapid transit station is a designated facility where passengers board, alight, and transfer between high-frequency urban rail or metro services, typically featuring platforms, ticketing areas, and access to surrounding streets or other transport modes.
-
E.
terminal station
A terminal station is a railway or transit station where a line or service ends, requiring trains or vehicles to reverse direction or terminate their routes.
- F. None of above. chosen
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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:10 p.m.