Triple

T17713453
Position Surface form Disambiguated ID Type / Status
Subject Utrechtse Heuvelrug E441626 entity
Predicate borderedBy P224 FINISHED
Object Wijk bij Duurstede 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: Wijk bij Duurstede | Statement: [Utrechtse Heuvelrug, borderedBy, Wijk bij Duurstede]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wijk bij Duurstede
Context triple: [Utrechtse Heuvelrug, borderedBy, Wijk bij Duurstede]
  • A. Wijk bij Duurstede chosen
    Wijk bij Duurstede is a historic Dutch town in the province of Utrecht, known for its medieval castle ruins, picturesque old center, and riverside setting.
  • B. Heemstede
    Heemstede is a town and municipality in the province of North Holland in the Netherlands, known as a leafy residential suburb near Haarlem.
  • C. Westwijk
    Westwijk is a residential district in Amstelveen, Netherlands, served as the southern terminus of Amsterdam’s former metro line 51.
  • D. Waalwijk
    Waalwijk is a town and municipality in the southern Netherlands known historically for its leather and shoe industry.
  • E. Steenwijk
    Steenwijk is a historic town in the Dutch province of Overijssel, known for its medieval center and role as a regional hub in the north of the province.
  • 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_69d8b9ea20b48190ace88bb46b01e6a9 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4729cebd08190872be96a26d0f7ce completed April 19, 2026, 6:13 a.m.
Created at: April 10, 2026, 10:06 a.m.