Triple
T5251523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isar |
E118598
|
entity |
| Predicate | hasBridge |
P386
|
FINISHED |
| Object | Maximiliansbrücke |
E520065
|
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: Maximiliansbrücke | Statement: [Isar, hasBridge, Maximiliansbrücke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maximiliansbrücke Context triple: [Isar, hasBridge, Maximiliansbrücke]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Ludwigsbrücke
chosen
Ludwigsbrücke is a historic bridge in Munich, Germany, spanning the Isar River and connecting the city center with the eastern districts.
-
E.
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.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b7b840881908bb1ecb8a0047382 |
completed | March 20, 2026, 4:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf486fb3f48190a07829bcb9d0f521 |
completed | March 22, 2026, 1:39 a.m. |
Created at: March 20, 2026, 1:50 p.m.