Triple

T17199352
Position Surface form Disambiguated ID Type / Status
Subject Elfstedentocht route E417436 entity
Predicate connects P390 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 route, connects, Hindeloopen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hindeloopen
Context triple: [Elfstedentocht route, connects, 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_69d886d6ba8c819093215917b3d01689 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42daddcd08190a82f36c940bf3f7b completed April 19, 2026, 1:19 a.m.
NED1 Entity disambiguation (via context triple) batch_6a01674bfabc8190bff7223e039089cc completed May 11, 2026, 5:21 a.m.
Created at: April 10, 2026, 5:38 a.m.