Triple

T13544066
Position Surface form Disambiguated ID Type / Status
Subject Lopik E323465 entity
Predicate isLocatedNear P350 FINISHED
Object IJsselstein 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: IJsselstein | Statement: [Lopik, isLocatedNear, IJsselstein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IJsselstein
Context triple: [Lopik, isLocatedNear, IJsselstein]
  • A. IJsselstein chosen
    IJsselstein is a historic Dutch town in the province of Utrecht, known for its medieval city center, castle ruins, and one of the tallest radio masts in the world.
  • B. Roosendaal
    Roosendaal is a city in the southern Netherlands known as a regional center for commerce and transport near the Belgian border.
  • C. Helmond
    Helmond is a city in the southern Netherlands known for its historic castle, industrial heritage, and location near Eindhoven in the province of North Brabant.
  • D. Valkenswaard
    Valkenswaard is a town in the southern Netherlands known for its strong equestrian culture and international show jumping events.
  • E. Doetinchem
    Doetinchem is a Dutch city in the eastern Netherlands, serving as a regional center in the Achterhoek area with a mix of historic charm and modern amenities.
  • 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_69d8076776248190bdf0d4fa1f85a5fc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbafda36248190acabde65a88c5471 completed April 12, 2026, 2:44 p.m.
Created at: April 9, 2026, 9:45 p.m.