Triple
T21158523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osnabrück–Bielefeld connections |
E521373
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway service grouping |
C20256
|
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: railway service grouping Context triple: [Osnabrück–Bielefeld connections, instanceOf, railway service grouping]
-
A.
railway line service pattern
chosen
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.
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.
-
C.
group of railway companies
A group of railway companies is an organized association of multiple rail transport operators that collaborate or are collectively managed to provide coordinated rail services, share resources, or pursue common commercial or regulatory interests.
-
D.
group of railway stations
A group of railway stations is a conceptual collection of multiple train stations considered together for purposes such as management, analysis, planning, or classification within a rail network.
-
E.
pre-grouping railway company
A pre-grouping railway company is a privately owned or regionally based railway operator in the United Kingdom that existed before the 1923 Railways Act consolidated most railways into the "Big Four" groups.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:59 p.m.