Triple

T17053031
Position Surface form Disambiguated ID Type / Status
Subject Losser E413748 entity
Predicate locatedNear P294 FINISHED
Object Bad Bentheim E326455 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: Bad Bentheim | Statement: [Losser, locatedNear, Bad Bentheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bad Bentheim
Context triple: [Losser, locatedNear, Bad Bentheim]
  • A. Bad Bentheim chosen
    Bad Bentheim is a historic spa town in Lower Saxony, Germany, best known for its medieval Bentheim Castle and therapeutic mineral springs.
  • B. Bad Suderode
    Bad Suderode is a spa village in the Harz region of central Germany, known for its mineral springs and health tourism.
  • C. Bad Honnef
    Bad Honnef is a spa town on the Rhine in North Rhine-Westphalia, Germany, known for its scenic setting near the Siebengebirge hills and its historical associations with prominent political figures.
  • D. Bad Düben
    Bad Düben is a small spa town in Saxony, Germany, known for its health resorts and location near the Dübener Heide nature park.
  • E. Bad Oeynhausen
    Bad Oeynhausen is a spa town in North Rhine-Westphalia, Germany, renowned for its thermal springs and health resorts.
  • 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_69d886cde3d481908d4d01ba88ba7eb7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3daa491008190ad013ee37532aa51 completed April 18, 2026, 7:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a012ed60d3481909c8144bcb01316a1 completed May 11, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:34 a.m.