Triple

T14189656
Position Surface form Disambiguated ID Type / Status
Subject Kennedybrücke (Hamburg) E351676 entity
Predicate locatedNear P294 FINISHED
Object Lombardsbrücke E254581 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: Lombardsbrücke | Statement: [Kennedybrücke (Hamburg), locatedNear, Lombardsbrücke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lombardsbrücke
Context triple: [Kennedybrücke (Hamburg), locatedNear, Lombardsbrücke]
  • A. Lombardsbrücke chosen
    Lombardsbrücke is a historic bridge in central Hamburg, Germany, spanning the Alster and serving as a key traffic and transport link in the city.
  • B. Rathausbrücke
    Rathausbrücke is a historic pedestrian bridge in central Zurich, Switzerland, spanning the Limmat River near the city hall and the old town.
  • C. Corneliusbrücke
    Corneliusbrücke is a historic bridge in Munich, Germany, spanning the Isar River and connecting central districts near the Museumsinsel.
  • D. 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.
  • E. Maximiliansbrücke
    Maximiliansbrücke is a historic bridge in Munich, Germany, that spans the Isar River and connects the city center with the Maximilianeum and surrounding districts.
  • 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_69d827894ac0819097803e57f3227b23 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61df628c8190ba3f557e2128dce5 completed April 14, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd280861fc81908c342fc229a526f3 completed May 8, 2026, 12:02 a.m.
Created at: April 10, 2026, 1:03 a.m.