Triple

T20858273
Position Surface form Disambiguated ID Type / Status
Subject Spree River E513539 entity
Predicate crossedBy P416 FINISHED
Object Weidendammer Bridge NE NERFINISHED

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: Weidendammer Bridge | Statement: [Spree River, crossedBy, Weidendammer Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Weidendammer Bridge
Context triple: [Spree River, crossedBy, Weidendammer Bridge]
  • A. Weidendammer Bridge chosen
    The Weidendammer Bridge is a historic cast-iron bridge in central Berlin, Germany, known for spanning the Spree River near Friedrichstraße and surviving World War II.
  • B. Lippe Bridge
    Lippe Bridge is a notable bridge in the German town of Lünen that spans the River Lippe and serves as a key local crossing and landmark.
  • C. Herdbrücke
    Herdbrücke is a historic bridge in Ulm, Germany, spanning the Danube and connecting the city center with the neighboring town of Neu-Ulm.
  • 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. Knesebeck Bridge
    Knesebeck Bridge is a bridge spanning the Teltow Canal in Berlin, Germany, serving as a local road and pedestrian crossing.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4f5b01081909452f654d2fc3f50 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c3a9fd7881908ae4c5c63f64efc0 completed April 21, 2026, 12:24 a.m.
Created at: April 16, 2026, 12:44 p.m.