Triple

T22565170
Position Surface form Disambiguated ID Type / Status
Subject Havelte region E557928 entity
Predicate contains P35 FINISHED
Object Havelte 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: Havelte | Statement: [Havelte region, contains, Havelte]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Havelte
Context triple: [Havelte region, contains, Havelte]
  • A. Havelte chosen
    Havelte is a village in the Dutch province of Drenthe, known for its nearby prehistoric dolmens and scenic natural surroundings.
  • B. Niederscheld
    Niederscheld is a village and district of the town of Dillenburg in the Lahn-Dill-Kreis of Hesse, Germany.
  • C. Bellingwedde
    Bellingwedde was a former municipality in the province of Groningen in the Netherlands, known for its rural landscape and small villages near the German border.
  • D. Vechta
    Vechta is a town in Lower Saxony, Germany, known for its historical significance, university, and annual Stoppelmarkt fair.
  • E. Waier
    Waier is a small island in Australia's Torres Strait, traditionally inhabited by Torres Strait Islander peoples who speak the Meriam Mir language.
  • 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_69e11e5ae4ac8190b1f503457603d969 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15fa9ebc8819098d74fb41e14bd7e completed April 29, 2026, 1:32 a.m.
Created at: April 16, 2026, 8:52 p.m.