Triple
T10104359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Service |
E216280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Amtrak train service brand |
C26839
|
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: Amtrak train service brand Context triple: [Silver Service, instanceOf, Amtrak train service brand]
-
A.
regional rail service brand
chosen
A regional rail service brand is a distinct identity used to market and organize passenger train services within a specific geographic area, encompassing naming, visual design, and service characteristics.
-
B.
high-speed rail service brand
A high-speed rail service brand is a distinct identity and marketing concept that represents a specific provider’s fast, long-distance passenger train services, encompassing its name, visual design, service standards, and customer experience.
-
C.
passenger rail service
Passenger rail service is a transportation system that operates trains to carry people between locations on a scheduled basis, typically offering various classes of comfort and amenities.
-
D.
Amtrak Thruway Motorcoach route
An Amtrak Thruway Motorcoach route is a scheduled bus service that connects passengers to and from Amtrak train stations, extending rail network coverage to areas not directly served by trains.
-
E.
Amtrak rolling stock
Amtrak rolling stock comprises the locomotives, passenger cars, and specialized rail vehicles owned or operated by Amtrak for intercity and regional passenger rail service in the United States.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 9:03 p.m.