Triple
T10546840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bochum |
E248839
|
entity |
| Predicate | hasRailwayStation |
P918
|
FINISHED |
| Object |
Bochum Hauptbahnhof
Bochum Hauptbahnhof is the main railway station and central transportation hub of the city of Bochum in Germany.
|
E870050
|
NE FINISHED |
How this triple was built (4 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: Bochum Hauptbahnhof | Statement: [Bochum, hasRailwayStation, Bochum Hauptbahnhof]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bochum Hauptbahnhof Context triple: [Bochum, hasRailwayStation, Bochum Hauptbahnhof]
-
A.
Dortmund Hauptbahnhof
Dortmund Hauptbahnhof is the main railway station and central transportation hub of the city of Dortmund in Germany.
-
B.
Düsseldorf Hauptbahnhof
Düsseldorf Hauptbahnhof is the main railway station of Düsseldorf and a major regional and long-distance transport hub in western Germany.
-
C.
Duisburg Hauptbahnhof
Duisburg Hauptbahnhof is the central railway station and major transportation hub serving the city of Duisburg in western Germany.
-
D.
Bonn-Beuel station
Bonn-Beuel station is a railway station in the Beuel district of Bonn, Germany, serving regional and local train services.
-
E.
Wuppertal Hauptbahnhof
Wuppertal Hauptbahnhof is the main railway station and central transport hub of the city of Wuppertal in western Germany.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Bochum Hauptbahnhof Triple: [Bochum, hasRailwayStation, Bochum Hauptbahnhof]
Generated description
Bochum Hauptbahnhof is the main railway station and central transportation hub of the city of Bochum in Germany.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Bochum Hauptbahnhof Target entity description: Bochum Hauptbahnhof is the main railway station and central transportation hub of the city of Bochum in Germany.
-
A.
Dortmund Hauptbahnhof
Dortmund Hauptbahnhof is the main railway station and central transportation hub of the city of Dortmund in Germany.
-
B.
Düsseldorf Hauptbahnhof
Düsseldorf Hauptbahnhof is the main railway station of Düsseldorf and a major regional and long-distance transport hub in western Germany.
-
C.
Duisburg Hauptbahnhof
Duisburg Hauptbahnhof is the central railway station and major transportation hub serving the city of Duisburg in western Germany.
-
D.
Bonn-Beuel station
Bonn-Beuel station is a railway station in the Beuel district of Bonn, Germany, serving regional and local train services.
-
E.
Wuppertal Hauptbahnhof
Wuppertal Hauptbahnhof is the main railway station and central transport hub of the city of Wuppertal in western Germany.
- F. None of above. chosen
Provenance (5 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d526d20ef48190ab9f70d4ce5f2a11 |
completed | April 7, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d9344a53fc81909765061d07d0cd20 |
completed | April 10, 2026, 5:32 p.m. |
| NEDg | Description generation | batch_69d938c8b25c8190bb048053d8668e5c |
completed | April 10, 2026, 5:52 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d939b1844881908c8fbcb9488863f6 |
completed | April 10, 2026, 5:56 p.m. |
Created at: April 6, 2026, 12:33 p.m.