Triple

T5924725
Position Surface form Disambiguated ID Type / Status
Subject Würzburg E131778 entity
Predicate hasBridge P386 FINISHED
Object Alte Mainbrücke E226308 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: Alte Mainbrücke | Statement: [Würzburg, hasBridge, Alte Mainbrücke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alte Mainbrücke
Context triple: [Würzburg, hasBridge, Alte Mainbrücke]
  • A. Alte Mainbrücke chosen
    Alte Mainbrücke is a historic stone bridge over the Main River in Würzburg, Germany, renowned for its baroque statues and scenic views of the city and Marienberg Fortress.
  • 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. 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.
  • D. Ludwigsbrücke
    Ludwigsbrücke is a historic bridge in Munich, Germany, spanning the Isar River and connecting the city center with the eastern districts.
  • E. 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.
  • 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_69c0085b75e88190a632f9691f9da48b completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03852806c81908ba726c16adf3358 completed March 22, 2026, 6:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c108186c64819088c21e9b5408d5f1 completed March 23, 2026, 9:30 a.m.
Created at: March 22, 2026, 4 p.m.