Triple
T34236830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitby (summer Saturdays, historically via Northern services) |
E878357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | seasonal rail service pattern |
C60649
|
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 rail service pattern Context triple: [Whitby (summer Saturdays, historically via Northern services), instanceOf, seasonal rail service pattern]
-
A.
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.
-
B.
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.
-
C.
public railway
A public railway is a government- or publicly-owned rail transport system that provides scheduled passenger and/or freight services accessible to the general population, typically operating on standardized tracks and infrastructure.
-
D.
railway service direction
A railway service direction specifies the intended travel orientation of a train service along a route, such as inbound, outbound, northbound, or southbound.
-
E.
railway route
A railway route is a defined path or corridor along which trains operate between specified locations, following designated tracks, schedules, and operational rules.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:56 a.m.