Triple

T23345346
Position Surface form Disambiguated ID Type / Status
Subject Hardbrücke tram stop E591841 entity
Predicate namedAfter P63 FINISHED
Object Hardbrücke 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: Hardbrücke | Statement: [Hardbrücke tram stop, namedAfter, Hardbrücke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hardbrücke
Context triple: [Hardbrücke tram stop, namedAfter, Hardbrücke]
  • A. Hardbrücke chosen
    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.
  • B. 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.
  • C. 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.
  • D. Krämerbrücke
    Krämerbrücke is a historic medieval bridge in Erfurt, Germany, famous for its densely packed, half-timbered houses built along its span and its role as a former merchants’ street.
  • E. Luitpoldbrücke
    Luitpoldbrücke is a historic bridge in Munich that spans the Isar River and connects key parts of the city along Prinzregentenstraße.
  • 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_69e25d20e3d08190bcede87673cafb25 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1983697408190b31817174ed4e77b completed April 29, 2026, 5:33 a.m.
Created at: April 17, 2026, 5:19 p.m.