Triple

T21158384
Position Surface form Disambiguated ID Type / Status
Subject historic center of Osnabrück E521369 entity
Predicate hasPart P35 FINISHED
Object Heger Tor 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: Heger Tor | Statement: [historic center of Osnabrück, hasPart, Heger Tor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heger Tor
Context triple: [historic center of Osnabrück, hasPart, Heger Tor]
  • A. Heger Tor chosen
    Heger Tor is a historic city gate in Osnabrück, Germany, known as a prominent remnant of the city’s former fortifications and a symbol of its old town.
  • B. Ellinger Tor
    Ellinger Tor is a historic city gate and one of the best-known architectural landmarks of the medieval town of Weißenburg in Bayern, Germany.
  • C. Hainbrunner Tor
    Hainbrunner Tor is a historic city gate in the town of Eberbach in southwestern Germany, notable as part of the town’s preserved medieval fortifications.
  • D. Hesselberg
    Hesselberg is a prominent hill in Bavaria, Germany, known as the highest elevation of the Franconian Alb region.
  • E. Stargarder Tor
    Stargarder Tor is a well-preserved medieval brick city gate in Neubrandenburg, Germany, renowned as one of the city's iconic defensive structures.
  • 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_69e0b50d1ea481909c07e63c3ead9316 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7252dc3f0819094c6acf52a9f308d completed April 21, 2026, 7:20 a.m.
Created at: April 16, 2026, 2:59 p.m.