Triple

T13684215
Position Surface form Disambiguated ID Type / Status
Subject Bunschoten E328079 entity
Predicate borderedBy P224 FINISHED
Object Nijkerk 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: Nijkerk | Statement: [Bunschoten, borderedBy, Nijkerk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nijkerk
Context triple: [Bunschoten, borderedBy, Nijkerk]
  • A. Nijkerk chosen
    Nijkerk is a historic town and municipality in the Dutch province of Gelderland in the central Netherlands.
  • B. Nijverdal
    Nijverdal is a town in the Dutch province of Overijssel known as a gateway to the Sallandse Heuvelrug National Park and its surrounding natural landscapes.
  • C. Nieuwendijk
    Nieuwendijk is one of Amsterdam’s oldest and busiest shopping streets, running through the historic city center near Dam Square.
  • D. Cuijk
    Cuijk is a historic town in the Dutch province of North Brabant, known for its Roman-era heritage and location along the River Meuse.
  • E. Heemskerk
    Heemskerk is a town and municipality in North Holland in the Netherlands, known for its coastal dunes, historic estates, and residential character.
  • 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_69d8076f1fa8819094664a59b55010df completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc66f8acc8190b2a82b722930b995 completed April 12, 2026, 4:21 p.m.
Created at: April 9, 2026, 9:53 p.m.