Triple

T20765463
Position Surface form Disambiguated ID Type / Status
Subject Verbotene Stadt E511083 entity
Predicate locatedIn P40 FINISHED
Object Wünsdorf 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: Wünsdorf | Statement: [Verbotene Stadt, locatedIn, Wünsdorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wünsdorf
Context triple: [Verbotene Stadt, locatedIn, Wünsdorf]
  • A. Wünsdorf chosen
    Wünsdorf is a town in Brandenburg, Germany, historically notable as a major military garrison and command center, including serving as the site of the German Wehrmacht’s high command during World War II.
  • B. Wiesdorf
    Wiesdorf is a central district of the German city of Leverkusen, known for its commercial areas and proximity to major industrial facilities.
  • C. Wietzendorf
    Wietzendorf is a small municipality in Lower Saxony, Germany, known for its rural character and location in the Lüneburg Heath region.
  • D. Heinersdorf
    Heinersdorf is a residential locality in the borough of Pankow in Berlin, Germany, known for its suburban character and proximity to the city center.
  • E. Wermsdorf
    Wermsdorf is a municipality in Saxony, Germany, best known as the site of the large Baroque hunting lodge and former royal residence Hubertusburg Palace.
  • 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_69e0b4ca01148190ac018e57e0cab46f completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c24bde0c8190b46986b89bf2e037 completed April 21, 2026, 12:18 a.m.
Created at: April 16, 2026, 12:36 p.m.