Triple
T28734263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDN |
E730750
|
entity |
| Predicate | associatedRailwayOperator |
P121930
|
FINISHED |
| Object | Deutsche Bahn |
E22662
|
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: Deutsche Bahn | Statement: [DDN, associatedRailwayOperator, Deutsche Bahn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRailwayOperator Context triple: [DDN, associatedRailwayOperator, Deutsche Bahn]
-
A.
hasRailTransportOperator
chosen
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
B.
railwayCompanyOnRoute
Indicates that a particular railway company operates or provides service on a specified route.
-
C.
railwayCompany
Indicates that one entity is a railway company that owns, operates, or manages railway services or infrastructure in relation to another entity.
-
D.
formerRailOperator
Indicates that an entity previously operated a rail service or railway system but no longer does so.
-
E.
hasNearbyRailwayOperator
Indicates that a railway operator is located close to or serves the vicinity of a given entity.
- F. None of above.
Provenance (4 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a01c303af6081909c229b2c8e91c680 |
completed | May 11, 2026, 11:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1ccf64ceec8190b8d00a021a6edaf7 |
completed | June 1, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_6a01c28ebf54819094318c447d8c7943 |
completed | May 11, 2026, 11:50 a.m. |
Created at: April 28, 2026, 5:59 a.m.