Triple
T37174068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helsinki commuter rail line D |
E920990
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | peak-hours train service |
C13511
|
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: peak-hours train service Context triple: [Helsinki commuter rail line D, instanceOf, peak-hours train service]
-
A.
rush-hour service
chosen
Rush-hour service is a transportation or customer service schedule that provides increased capacity or frequency during peak demand periods to accommodate higher user volumes efficiently.
-
B.
seasonal rail service pattern
A seasonal rail service pattern is a timetable configuration in which train frequencies, routes, or stopping patterns vary systematically between different times of the year to match seasonal demand, weather conditions, or operational constraints.
-
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.
railway line service pattern
A railway line service pattern defines the structured arrangement of train services over a route, including stopping sequences, frequencies, and service types that determine how trains operate along the line.
-
E.
passenger train
A passenger train is a rail vehicle or series of connected vehicles designed to transport people and their luggage between stations along a fixed route and schedule.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.