Triple

T23201604
Position Surface form Disambiguated ID Type / Status
Subject Hekelingen E580326 entity
Predicate nearbyTown P3883 FINISHED
Object Spijkenisse 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: Spijkenisse | Statement: [Hekelingen, nearbyTown, Spijkenisse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Spijkenisse
Context triple: [Hekelingen, nearbyTown, Spijkenisse]
  • A. Spijkenisse chosen
    Spijkenisse is a town and former municipality in the western Netherlands, now part of the municipality of Nissewaard and known as a suburban area near Rotterdam.
  • B. Sparnacien
    Sparnacien is the French demonym for an inhabitant of the town of Épernay in the Champagne region.
  • C. Winkel van Sinkel
    Winkel van Sinkel is a historic former department store and cultural landmark in the center of Utrecht, Netherlands, now used as a venue for events, dining, and nightlife.
  • D. Spicheren
    Spicheren is a commune in northeastern France near the German border, historically notable as the site of a major battle in the Franco-Prussian War.
  • E. Zesgehuchten
    Zesgehuchten was a former village and municipality in the Dutch province of North Brabant, now part of the city of Geldrop-Mierlo.
  • 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_69e24602ae1481908aaa6bc7ca493867 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f19079c44881909e8677921b08b931 completed April 29, 2026, 5 a.m.
Created at: April 17, 2026, 4:06 p.m.