Triple
T17127965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mainz Hauptbahnhof |
E415647
|
entity |
| Predicate | owner |
P347
|
FINISHED |
| Object | DB Netz |
E390675
|
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 Netz | Statement: [Mainz Hauptbahnhof, owner, DB Netz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DB Netz Context triple: [Mainz Hauptbahnhof, owner, DB Netz]
-
A.
DB Netz
DB Netz is the infrastructure division of Deutsche Bahn responsible for operating and maintaining Germany’s national railway network.
-
B.
DB Netz AG
chosen
DB Netz AG is a subsidiary of Deutsche Bahn responsible for operating and maintaining Germany’s national railway infrastructure network.
-
C.
Netze
Netze is the German name for the Noteć, a river in north-central Poland that is a tributary of the Warta.
-
D.
DBE
DBE is the title "Dame Commander of the Order of the British Empire," a high-ranking honor awarded in the British honours system.
-
E.
DSN
DSN is the acronym for NASA’s Deep Space Network, a global system of large radio antennas used to communicate with and track interplanetary spacecraft and distant space missions.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f0285a408190ae5e4c4679c07fbf |
completed | April 18, 2026, 8:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01414a51d4819086c2346fe2d4fce4 |
completed | May 11, 2026, 2:39 a.m. |
Created at: April 10, 2026, 5:36 a.m.