Triple

T17053137
Position Surface form Disambiguated ID Type / Status
Subject Hellendoorn E413750 entity
Predicate borders P224 FINISHED
Object Ommen E547511 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: Ommen | Statement: [Hellendoorn, borders, Ommen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ommen
Context triple: [Hellendoorn, borders, Ommen]
  • A. Ommen chosen
    Ommen is a small historic town and municipality in the Dutch province of Overijssel, known for its scenic river landscapes and tourism.
  • B. Olman
    Olman is a surname most notably associated with Abe Olman, an American songwriter and music publisher active in the early 20th century.
  • C. Orma
    Orma is a major dialect of the Oromo language spoken primarily by the Orma people of Kenya.
  • D. Hannut
    Hannut is a municipality in the French-speaking Walloon Region of Belgium, known for its rural character and location between Liège and Brussels.
  • E. Hemulen
    Hemulen is a character from Tove Jansson’s Moomin series, typically portrayed as a tall, earnest, and somewhat pedantic creature obsessed with hobbies like stamp collecting and botany.
  • 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_6a012343eca0819086a07511c5d22878 completed May 11, 2026, 12:31 a.m.
Created at: April 10, 2026, 5:34 a.m.