Triple
T22097936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London (seasonal Eurostar) |
E546086
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | seasonal high-speed train service |
C75
|
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: seasonal high-speed train service Context triple: [London (seasonal Eurostar), instanceOf, seasonal high-speed train service]
-
A.
passenger rail service
chosen
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.
-
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.
intercity coach service
An intercity coach service is a scheduled, long-distance bus transportation system that carries passengers between cities or towns, typically offering reserved seating, luggage capacity, and limited intermediate stops.
-
D.
rapid rail system
A rapid rail system is a high-speed, high-capacity railway network designed to transport large numbers of passengers quickly and efficiently between urban or regional destinations using dedicated tracks and frequent service.
-
E.
high-speed test train
A high-speed test train is a specialized railway vehicle designed to operate at very high velocities to evaluate, validate, and optimize track infrastructure, signaling systems, and rolling stock performance under extreme operating conditions.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:30 p.m.