Triple

T17310818
Position Surface form Disambiguated ID Type / Status
Subject Elfstedentocht E420288 entity
Predicate passesThrough P225 FINISHED
Object Hindeloopen E420291 NE FINISHED

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: Hindeloopen | Statement: [Elfstedentocht, passesThrough, Hindeloopen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hindeloopen
Context triple: [Elfstedentocht, passesThrough, Hindeloopen]
  • A. Hindeloopen chosen
    Hindeloopen is a small historic town in the Dutch province of Friesland, renowned for its traditional painted folk art and picturesque canals.
  • B. Oirschot
    Oirschot is a historic municipality and town in the Dutch province of North Brabant, known for its well-preserved medieval center and cultural heritage.
  • C. Zandvoort
    Zandvoort is a Dutch coastal town on the North Sea known for its sandy beaches and the nearby Circuit Zandvoort motor racing track.
  • D. Apeldoorn, Netherlands
    Apeldoorn is a city in the province of Gelderland in the central Netherlands, known for the royal palace Het Loo and its surrounding forests and parks.
  • E. Korendijk
    Korendijk was a former municipality in the Dutch province of South Holland that later became part of the larger municipality of Hoeksche Waard.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d889d22b848190a4663d0b8f8f76e7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4399837b08190b7cf74201b3cb013 completed April 19, 2026, 2:10 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0180e5043081908f31c2434e9b9647 completed May 11, 2026, 7:10 a.m.
Created at: April 10, 2026, 5:43 a.m.