Triple

T12075608
Position Surface form Disambiguated ID Type / Status
Subject Steenwijkerland E287537 entity
Predicate hasHistoricCenter P295 FINISHED
Object Steenwijk 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: Steenwijk | Statement: [Steenwijkerland, hasHistoricCenter, Steenwijk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Steenwijk
Context triple: [Steenwijkerland, hasHistoricCenter, Steenwijk]
  • A. Steenwijk chosen
    Steenwijk is a historic town in the Dutch province of Overijssel, known for its medieval center and role as a regional hub in the north of the province.
  • B. Harderwijk
    Harderwijk is a historic Dutch city known for its former Hanseatic trading role and scenic location on the shores of the Veluwemeer.
  • C. Waalwijk
    Waalwijk is a town and municipality in the southern Netherlands known historically for its leather and shoe industry.
  • D. Winterswijk
    Winterswijk is a town in the eastern Netherlands known for its rural landscape, textile-industry history, and location near the German border.
  • E. Schoonhoven
    Schoonhoven is a historic Dutch town in South Holland, renowned for its silver craftsmanship and picturesque riverside setting.
  • 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.