Triple

T19187813
Position Surface form Disambiguated ID Type / Status
Subject Burgring E469749 entity
Predicate hasNearbyLandmark P2064 FINISHED
Object Burgtor 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: Burgtor | Statement: [Burgring, hasNearbyLandmark, Burgtor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burgtor
Context triple: [Burgring, hasNearbyLandmark, Burgtor]
  • A. Burgtor chosen
    Burgtor is a historic city gate in Lübeck, Germany, notable as part of the city’s medieval fortifications and Hanseatic architectural heritage.
  • B. Stadttor
    Stadttor is a prominent modern office and government building in Düsseldorf, Germany, known for its distinctive glass architecture and role as a landmark of the MedienHafen area.
  • C. Frauentor
    Frauentor is a historic city gate in Nuremberg, Germany, notable as one of the main entrances through the medieval fortifications into the old town.
  • D. Carmental Gate
    Carmental Gate was an ancient city gate in Rome’s early defensive walls, serving as a key western entrance near the Tiber and associated with important religious and historical traditions.
  • E. Enderttor city gate
    Enderttor city gate is a historic medieval gate and former fortification in the town of Cochem, Germany.
  • 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_69d8dd0ad9088190a173b32657ae2e7a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f89f3ebc8190ba01ae075ffc77df completed April 20, 2026, 9:57 a.m.
Created at: April 10, 2026, 12:07 p.m.