Triple
T7064929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulm–Sigmaringen railway |
E164321
|
entity |
| Predicate | serviceOperator |
P5884
|
FINISHED |
| Object | DB Regio |
E119083
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: DB Regio | Statement: [Ulm–Sigmaringen railway, serviceOperator, DB Regio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DB Regio Context triple: [Ulm–Sigmaringen railway, serviceOperator, DB Regio]
-
A.
DB Regio
chosen
DB Regio is a division of Germany’s national railway company that operates most of the country’s regional and local passenger train services.
-
B.
DB Regio Bus
DB Regio Bus is the regional and local bus transport division of Deutsche Bahn, operating extensive bus services across Germany.
-
C.
DB Netz (for most lines)
DB Netz is the rail infrastructure division of Deutsche Bahn responsible for operating and maintaining most of Germany’s railway network.
-
D.
DB Station&Service
DB Station&Service is a subsidiary of Deutsche Bahn responsible for managing and operating railway stations across Germany.
-
E.
ProRail
ProRail is the Dutch government-owned company responsible for managing and maintaining the national railway infrastructure in the Netherlands.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c788ba7af88190aeaf3205255af8ad |
completed | March 28, 2026, 7:52 a.m. |
Created at: March 27, 2026, 2:39 p.m.