Triple
T7040166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwich to Sheringham |
E163489
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional rail passenger 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: regional rail passenger service Context triple: [Norwich to Sheringham, instanceOf, regional rail passenger 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.
commuter rail line
A commuter rail line is a passenger train service that operates on fixed tracks and schedules to connect suburban or outlying areas with a central city, primarily serving daily work and school commuters.
-
C.
suburban commuter train
A suburban commuter train is a passenger rail service designed to transport people efficiently between residential suburbs and urban centers, typically operating on fixed schedules with frequent stops during peak travel times.
-
D.
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.
-
E.
named passenger train
A named passenger train is a specific, regularly scheduled train service distinguished by a unique name and consistent route, amenities, and branding for carrying passengers.
- 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_69c6885e7c1c8190be32a8f79ab4e0cf |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:36 p.m.