Triple

T20725618
Position Surface form Disambiguated ID Type / Status
Subject Waalwijk E509426 entity
Predicate locatedNear P294 FINISHED
Object Kaatsheuvel 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: Kaatsheuvel | Statement: [Waalwijk, locatedNear, Kaatsheuvel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kaatsheuvel
Context triple: [Waalwijk, locatedNear, Kaatsheuvel]
  • A. Kaatsheuvel chosen
    Kaatsheuvel is a Dutch village best known as the home of the Efteling theme park, one of Europe’s largest and oldest amusement parks.
  • B. Veenendaal
    Veenendaal is a Dutch town and municipality in the central Netherlands, known for its location between Utrecht and the Veluwe and its mix of residential, commercial, and light industrial areas.
  • C. Schoorl
    Schoorl is a coastal village in North Holland, the Netherlands, known for its extensive dune landscapes and as the birthplace of Renaissance painter Jan van Scorel.
  • D. Nieuwenhoorn
    Nieuwenhoorn is a village in the western Netherlands that forms part of the province of South Holland.
  • E. Uithoorn
    Uithoorn is a town and municipality in the province of North Holland in the Netherlands, situated along the Amstel River.
  • 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_69e0b4c4cc648190b45fda6e2b20af56 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c1e7aabc819084f9e9fd45e877fd completed April 21, 2026, 12:16 a.m.
Created at: April 16, 2026, 12:29 p.m.