Triple

T15838660
Position Surface form Disambiguated ID Type / Status
Subject Samtgemeinde Faßberg E384045 entity
Predicate locatedNear P294 FINISHED
Object Wietzendorf E690005 NE FINISHED

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: Wietzendorf | Statement: [Samtgemeinde Faßberg, locatedNear, Wietzendorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wietzendorf
Context triple: [Samtgemeinde Faßberg, locatedNear, Wietzendorf]
  • A. Wietzendorf chosen
    Wietzendorf is a small municipality in Lower Saxony, Germany, known for its rural character and location in the Lüneburg Heath region.
  • B. Perasdorf
    Perasdorf is a small municipality in the Straubing-Bogen district of Lower Bavaria, Germany.
  • C. Wiesdorf
    Wiesdorf is a central district of the German city of Leverkusen, known for its commercial areas and proximity to major industrial facilities.
  • D. Rüngsdorf
    Rüngsdorf is a residential district in the southern part of Bonn, Germany, known for its scenic location along the Rhine and its affiliation with the Bad Godesberg borough.
  • E. Wünsdorf
    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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e142e4fa24819086a1a226082ac2d3 completed April 16, 2026, 8:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffc3b717c88190b974a44470136ff2 completed May 9, 2026, 11:31 p.m.
Created at: April 10, 2026, 4:49 a.m.