Triple

T18377907
Position Surface form Disambiguated ID Type / Status
Subject Fleischbrücke E446363 entity
Predicate hasLocaleName P72248 FINISHED
Object Fleischbrü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: Fleischbrücke | Statement: [Fleischbrücke, hasLocaleName, Fleischbrücke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fleischbrücke
Context triple: [Fleischbrücke, hasLocaleName, Fleischbrücke]
  • A. Fleischbrücke chosen
    Fleischbrücke is a historic stone arch bridge in Nuremberg, Germany, renowned for its Renaissance architecture and role as a key crossing in the city center.
  • B. Bösebrücke
    Bösebrücke is a historic Berlin bridge best known as the site of the first border crossing opened during the fall of the Berlin Wall on November 9, 1989.
  • C. Friedensbrücke
    Friedensbrücke is a notable bridge in the city of Plauen, Germany, recognized as a local landmark and important traffic connection.
  • D. Tuchlauben
    Tuchlauben is a historic street in Vienna’s city center, known for its upscale shops and proximity to major landmarks in the old town.
  • E. Draubrücke
    Draubrücke is a bridge in the Austrian city of Villach that spans the Drava (Drau) River and serves as an important local traffic connection.
  • 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_69d8b9f370b88190b1e5081c2c238e7f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e5179919c881908d55ea24f93c5827 completed April 19, 2026, 5:57 p.m.
Created at: April 10, 2026, 10:45 a.m.