Triple

T14185541
Position Surface form Disambiguated ID Type / Status
Subject island of Voorne-Putten E351564 entity
Predicate contains P35 FINISHED
Object Bernisse 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: Bernisse | Statement: [island of Voorne-Putten, contains, Bernisse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bernisse
Context triple: [island of Voorne-Putten, contains, Bernisse]
  • A. Bernisse chosen
    Bernisse is a waterway in the South Holland province of the Netherlands, known for connecting several polders and serving as a recreational and natural area.
  • B. Beverwijk
    Beverwijk is a town and municipality in North Holland, Netherlands, known for its large indoor market and proximity to the North Sea coast.
  • C. Barendrecht
    Barendrecht is a suburban town in the western Netherlands, located just south of Rotterdam and known for its residential character and logistics industry.
  • D. Leidschendam-Voorburg
    Leidschendam-Voorburg is a municipality in the western Netherlands, near The Hague, formed by the towns of Leidschendam and Voorburg.
  • E. Voorhout
    Voorhout is a village in South Holland, Netherlands, that forms part of the municipality of Teylingen.
  • 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_69d8278834a08190b0f1784e58d7b99c completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61cd5778819092a03597bcdcc182 completed April 14, 2026, 3:48 p.m.
Created at: April 10, 2026, 1:03 a.m.