Triple
T10290775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binnenalster |
E241355
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Lombardsbrücke |
E254581
|
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: Lombardsbrücke | Statement: [Binnenalster, borderedBy, Lombardsbrücke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lombardsbrücke Context triple: [Binnenalster, borderedBy, Lombardsbrücke]
-
A.
Lombardsbrücke
chosen
Lombardsbrücke is a historic bridge in central Hamburg, Germany, spanning the Alster and serving as a key traffic and transport link in the city.
-
B.
Rathausbrücke
Rathausbrücke is a historic pedestrian bridge in central Zurich, Switzerland, spanning the Limmat River near the city hall and the old town.
-
C.
Luitpoldbrücke
Luitpoldbrücke is a historic bridge in Munich that spans the Isar River and connects key parts of the city along Prinzregentenstraße.
-
D.
Schlossbrücke
Schlossbrücke is a historic bridge in central Berlin that spans the Spree River, connecting Unter den Linden with Museum Island near the Berlin Palace.
-
E.
Knesebeck Bridge
Knesebeck Bridge is a bridge spanning the Teltow Canal in Berlin, Germany, serving as a local road and pedestrian crossing.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d281348190bac00cf826689cd7 |
completed | April 7, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d794c79ae88190b80c805f7671e264 |
completed | April 9, 2026, noon |
Created at: April 6, 2026, 11:41 a.m.