Triple

T22316699
Position Surface form Disambiguated ID Type / Status
Subject Chapel Bridge E551663 entity
Predicate alsoKnownAs P39 FINISHED
Object Kapellbrü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: Kapellbrücke | Statement: [Chapel Bridge, alsoKnownAs, Kapellbrücke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kapellbrücke
Context triple: [Chapel Bridge, alsoKnownAs, Kapellbrücke]
  • A. Kapellbrücke chosen
    Kapellbrücke is a historic 14th-century covered wooden footbridge in Lucerne, Switzerland, famous for its interior paintings and iconic water tower.
  • B. Marienbrücke
    Marienbrücke is a famous pedestrian bridge near Neuschwanstein Castle in Bavaria, Germany, renowned for its panoramic views of the castle and the surrounding gorge.
  • C. 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.
  • 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. 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 (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_69e11e4776588190abb21e5cea79973f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f157535eb48190adbefbb619cb5fcd completed April 29, 2026, 12:56 a.m.
Created at: April 16, 2026, 8:42 p.m.