Triple
T8662457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Kiel |
E205579
|
entity |
| Predicate | hasTerminal |
P182
|
FINISHED |
| Object | Bahnhofsbrücke |
E542779
|
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: Bahnhofsbrücke | Statement: [Port of Kiel, hasTerminal, Bahnhofsbrücke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bahnhofsbrücke Context triple: [Port of Kiel, hasTerminal, Bahnhofsbrücke]
-
A.
Bahnhofbrücke
chosen
Bahnhofbrücke is a central bridge in Zurich that connects the main railway station area with the city’s inner districts across the Limmat River.
-
B.
Hardbrücke
Hardbrücke is a major road and railway bridge in Zurich, Switzerland, serving as an important traffic artery across the Limmat and nearby rail tracks.
-
C.
Mühlendamm bridge
The Mühlendamm Bridge is a historic bridge in central Berlin that spans the Spree River, connecting key parts of the city’s old town area.
-
D.
Julius-Leber-Brücke bridge
Julius-Leber-Brücke bridge is a railway overpass in Berlin, Germany, known for carrying train tracks over city streets in the Schöneberg district.
-
E.
Karl-Theodor-Brücke
Karl-Theodor-Brücke is the official name of Heidelberg’s historic Old Bridge, a famous stone arch bridge spanning the Neckar River in Germany.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4872a190819087d679f3006bd030 |
completed | March 31, 2026, 10:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cecd0518248190ba0d3a87d11dff86 |
completed | April 2, 2026, 8:09 p.m. |
Created at: March 30, 2026, 6:30 p.m.