Triple

T23553697
Position Surface form Disambiguated ID Type / Status
Subject Jannowitzbrücke E578121 entity
Predicate locatedOn P40 FINISHED
Object Jannowitzbrücke 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: Jannowitzbrücke bridge | Statement: [Jannowitzbrücke, locatedOn, Jannowitzbrücke bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jannowitzbrücke bridge
Context triple: [Jannowitzbrücke, locatedOn, Jannowitzbrücke bridge]
  • A. Jannowitzbrücke chosen
    Jannowitzbrücke is a Berlin U-Bahn and S-Bahn station located near the River Spree in the city center, serving as a key transit point on several urban rail lines.
  • B. Glienicke Bridge, Berlin
    Glienicke Bridge in Berlin is a historic span over the Havel River that became famous during the Cold War as a key site for high-profile prisoner exchanges between East and West.
  • C. Kaisermühlenbrücke
    Kaisermühlenbrücke is a bridge in the Kaisermühlen district of Vienna, Austria, serving as a key crossing over the Danube.
  • D. Dammbrücke Köpenick
    Dammbrücke Köpenick is a bridge in the Berlin district of Köpenick that spans one of the local waterways, connecting parts of the historic town area.
  • E. Hardbrücke
    Hardbrücke is a major road and railway bridge in Zurich, Switzerland, serving as an important traffic artery across the Limmat and nearby rail tracks.
  • 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_69e245fa93448190919cb04534560542 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1aed17fc881908b45dcde14790d42 completed April 29, 2026, 7:10 a.m.
Created at: April 17, 2026, 6:11 p.m.