Triple
T21158550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DB Netz regional division responsible for Lower Saxony |
E521374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subsidiary organization of Deutsche Bahn |
C9409
|
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: subsidiary organization of Deutsche Bahn Context triple: [DB Netz regional division responsible for Lower Saxony, instanceOf, subsidiary organization of Deutsche Bahn]
-
A.
private railway company
A private railway company is a non-governmental business entity that owns, operates, or manages rail transport services for passengers and/or freight, typically for profit under regulatory oversight.
-
B.
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.
-
C.
InterCityExpress variant
An InterCityExpress variant is a specific model or configuration of high-speed ICE train designed for particular routes, capacities, or service requirements within an intercity rail network.
-
D.
rail transport company
chosen
A rail transport company is an organization that owns, operates, or manages trains and railway infrastructure to provide freight and/or passenger transportation services.
-
E.
Berlin S-Bahn service
Berlin S-Bahn service is a rapid transit and suburban rail network that provides frequent, high-capacity train connections across Berlin and its surrounding metropolitan region.
- 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.