Triple

T14186863
Position Surface form Disambiguated ID Type / Status
Subject Bernisse E351599 entity
Predicate borderedBy P224 FINISHED
Object Westvoorne E1098482 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: Westvoorne | Statement: [Bernisse, borderedBy, Westvoorne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Westvoorne
Context triple: [Bernisse, borderedBy, Westvoorne]
  • A. Westvoorne chosen
    Westvoorne is a coastal municipality in the Dutch province of South Holland, known for its beaches, dunes, and nature reserves.
  • B. Nijverdal
    Nijverdal is a town in the Dutch province of Overijssel known as a gateway to the Sallandse Heuvelrug National Park and its surrounding natural landscapes.
  • C. 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.
  • D. Vollenhoven
    Vollenhoven is a Dutch surname most notably associated with philosopher D. H. Th. Vollenhoven, a key figure in Reformational philosophy.
  • E. Molenwaard
    Molenwaard was a former municipality in the Dutch province of South Holland that later became part of the newly formed municipality of Molenlanden.
  • 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_69d8278834a08190b0f1784e58d7b99c completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61cd5778819092a03597bcdcc182 completed April 14, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69fffee0ff948190911c02f6e50ea2bc completed May 10, 2026, 3:43 a.m.
Created at: April 10, 2026, 1:03 a.m.