Triple

T12866621
Position Surface form Disambiguated ID Type / Status
Subject Kornhausbrücke (Bern) E307735 entity
Predicate hasLocalName P6353 FINISHED
Object Kornhausbrücke E391097 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: Kornhausbrücke | Statement: [Kornhausbrücke (Bern), hasLocalName, Kornhausbrücke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kornhausbrücke
Context triple: [Kornhausbrücke (Bern), hasLocalName, Kornhausbrücke]
  • A. Kornhausbrücke chosen
    Kornhausbrücke is a historic bridge in Bern, Switzerland, spanning the Aare River and connecting the Old City with newer districts.
  • B. Kornhausbrücke
    Kornhausbrücke is a bridge in Zurich, Switzerland, that carries traffic across the Limmat River near the city’s historic center.
  • C. Krämerbrücke
    Krämerbrücke is a historic medieval bridge in Erfurt, Germany, famous for its densely packed, half-timbered houses built along its span and its role as a former merchants’ street.
  • 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. 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.
  • 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_69d7bdf69bc48190af6c2621f28ca351 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9708e0b788190b72a3057e271c227 completed April 10, 2026, 9:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f69bb092b88190b159f1d79156cf86 completed May 3, 2026, 12:49 a.m.
Created at: April 9, 2026, 5:38 p.m.