Triple

T15975396
Position Surface form Disambiguated ID Type / Status
Subject Nydegg Bridge E387430 entity
Predicate follows P134 FINISHED
Object Untertorbrücke E442884 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: Untertorbrücke | Statement: [Nydegg Bridge, follows, Untertorbrücke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Untertorbrücke
Context triple: [Nydegg Bridge, follows, Untertorbrücke]
  • A. Untertorbrücke chosen
    Untertorbrücke is a historic stone bridge in Bern, Switzerland, spanning the Aare River and connecting parts of the city’s medieval 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. Boschbrücke
    Boschbrücke is a bridge in Munich, Germany, that connects to the Museumsinsel (Museum Island) over the Isar River.
  • D. Ziegelgraben Bridge
    Ziegelgraben Bridge is the movable opening bridge section of the Rügendamm causeway connecting the German island of Rügen to the mainland.
  • E. Yorckbrücken
    Yorckbrücken is a series of historic railway bridges in Berlin, Germany, known for their dense concentration and industrial architectural character.
  • 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_69d86da94ccc819083d187f5dc6a123e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1572c216c81908f2070d2a87609c2 completed April 16, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fff794c8508190a444af7ce968c5da completed May 10, 2026, 3:12 a.m.
Created at: April 10, 2026, 4:54 a.m.