Triple

T5543399
Position Surface form Disambiguated ID Type / Status
Subject Unter den Linden E145347 entity
Predicate easternTerminus P388 FINISHED
Object Schlossbrücke E147104 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: Schlossbrücke | Statement: [Unter den Linden, easternTerminus, Schlossbrücke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schlossbrücke
Context triple: [Unter den Linden, easternTerminus, Schlossbrücke]
  • A. Schlossbrücke chosen
    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. 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. 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.
  • 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_69c008fa64888190adae56c8f9ea4031 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01fc947bc81908d1f7b709392ec20 completed March 22, 2026, 4:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69c059df62ac8190865dda631da4cec0 completed March 22, 2026, 9:06 p.m.
Created at: March 22, 2026, 3:35 p.m.