Triple

T20523196
Position Surface form Disambiguated ID Type / Status
Subject Tönning E503863 entity
Predicate nearbyCity P350 FINISHED
Object Heide 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: Heide | Statement: [Tönning, nearbyCity, Heide]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heide
Context triple: [Tönning, nearbyCity, Heide]
  • A. Heide chosen
    Heide is a small German town that serves as the administrative center of the Dithmarschen district in the state of Schleswig-Holstein.
  • B. Heidiland
    Heidiland is a popular Swiss tourist region in Eastern Switzerland, known for its alpine landscapes and associations with Johanna Spyri’s "Heidi" stories.
  • C. Örtze
    Örtze is a river in Lower Saxony, Germany, known for flowing through the Lüneburg Heath before joining the Aller.
  • D. Wiehe
    Wiehe is a small town in the German state of Thuringia, historically notable as the birthplace of the influential 19th-century historian Leopold von Ranke.
  • E. Heilsberg
    Heilsberg is a historic town in northeastern Poland, known today as Lidzbark Warmiński, that was the site of significant medieval and Napoleonic-era military engagements.
  • 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_69e0b4b3a6e08190ae663701f50fab8e completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69f471f18819091e8a57161fe0225 completed April 20, 2026, 9:48 p.m.
Created at: April 16, 2026, 11:36 a.m.