Triple

T17766972
Position Surface form Disambiguated ID Type / Status
Subject Halberstadt E443531 entity
Predicate locatedOnRiver P165 FINISHED
Object Holtemme 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: Holtemme | Statement: [Halberstadt, locatedOnRiver, Holtemme]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Holtemme
Context triple: [Halberstadt, locatedOnRiver, Holtemme]
  • A. Holtemme chosen
    The Holtemme is a small river in the Harz region of Saxony-Anhalt, Germany, flowing through towns such as Wernigerode before joining the Bode.
  • B. Holsen
    Holsen is a village and district of the town of Bünde in North Rhine-Westphalia, Germany.
  • C. Hulten
    Hulten is a small village in the Dutch province of North Brabant, located within the municipality of Gilze en Rijen.
  • D. Hodenhagen
    Hodenhagen is a small municipality in Lower Saxony, Germany, known for its rural setting along the Aller River and proximity to attractions like the Serengeti Park safari zoo.
  • E. Holleken
    Holleken is a local railway station serving the suburban area near Brussels, Belgium.
  • 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_69d8b9edf16c8190a59ebd245d378f4f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e485fccb9881908923564bf319f3c1 completed April 19, 2026, 7:36 a.m.
Created at: April 10, 2026, 10:11 a.m.