Triple

T12075581
Position Surface form Disambiguated ID Type / Status
Subject Steenwijkerland E287537 entity
Predicate hasTown P847 FINISHED
Object Vollenhove 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: Vollenhove | Statement: [Steenwijkerland, hasTown, Vollenhove]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vollenhove
Context triple: [Steenwijkerland, hasTown, Vollenhove]
  • A. Vollenhove chosen
    Vollenhove is a historic town in the Dutch province of Overijssel, known for its former status as a regional administrative and noble center with several notable estates and churches.
  • B. Veldhoven
    Veldhoven is a town and municipality in the southern Netherlands, located near Eindhoven in the province of North Brabant.
  • C. Vollenhoven
    Vollenhoven is a Dutch surname most notably associated with philosopher D. H. Th. Vollenhoven, a key figure in Reformational philosophy.
  • D. Hansweert
    Hansweert is a small village in the Dutch province of Zeeland, known historically as a canal and shipping hub along the Western Scheldt.
  • E. Veenendaal
    Veenendaal is a Dutch town and municipality in the central Netherlands, known for its location between Utrecht and the Veluwe and its mix of residential, commercial, and light industrial areas.
  • 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_69d6ab4846e081908ee7bbd66a6d3459 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9045ceeec81909427cae8972eed26 completed April 10, 2026, 2:08 p.m.
Created at: April 8, 2026, 9:48 p.m.