Triple

T5247199
Position Surface form Disambiguated ID Type / Status
Subject Limmat River E118490 entity
Predicate crossedBy P416 FINISHED
Object Rathausbrü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: Rathausbrücke | Statement: [Limmat River, crossedBy, Rathausbrücke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rathausbrücke
Context triple: [Limmat River, crossedBy, Rathausbrü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. 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.
  • C. Kornhausbrücke
    Kornhausbrücke is a historic bridge in Bern, Switzerland, spanning the Aare River and connecting the Old City with newer districts.
  • D. Lombardsbrücke
    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.
  • E. Quaibrücke
    Quaibrücke is a prominent road and tram bridge in central Zurich, Switzerland, connecting the old town with the lakeside area where the Limmat River flows out of Lake Zurich.
  • 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_69bd4468aacc8190a8196f71855cdf4f completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7b5320748190bcf3be4b6c364f92 completed March 20, 2026, 4:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69befe68e1148190b2e3cc1f9e49dbbf completed March 21, 2026, 8:24 p.m.
Created at: March 20, 2026, 1:50 p.m.