Triple
T14868176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadthaus Zürich |
E349671
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Stadthausbrücke |
E352212
|
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: Stadthausbrücke | Statement: [Stadthaus Zürich, locatedOn, Stadthausbrücke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stadthausbrücke Context triple: [Stadthaus Zürich, locatedOn, Stadthausbrücke]
-
A.
Rathausbrücke
chosen
Rathausbrücke is a historic pedestrian bridge in central Zurich, Switzerland, spanning the Limmat River near the city hall and the old town.
-
B.
Maximiliansbrücke
Maximiliansbrücke is a historic bridge in Munich, Germany, that spans the Isar River and connects the city center with the Maximilianeum and surrounding districts.
-
C.
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.
-
D.
Kornhausbrücke
Kornhausbrücke is a bridge in Zurich, Switzerland, that carries traffic across the Limmat River near the city’s historic center.
-
E.
Kornhausbrücke
Kornhausbrücke is a historic bridge in Bern, Switzerland, spanning the Aare River and connecting the Old City with newer districts.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5776b848190bfe3a06ff261dc31 |
completed | April 15, 2026, 12:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe651067cc8190b9c218ef1f802762 |
completed | May 8, 2026, 10:34 p.m. |
Created at: April 10, 2026, 1:55 a.m.