Triple

T14186719
Position Surface form Disambiguated ID Type / Status
Subject Westvoorne E351596 entity
Predicate contains P35 FINISHED
Object Oostvoorne E119127 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: Oostvoorne | Statement: [Westvoorne, contains, Oostvoorne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oostvoorne
Context triple: [Westvoorne, contains, Oostvoorne]
  • A. Oostvoorne chosen
    Oostvoorne is a coastal village in the western Netherlands known for its dunes, beaches, and nature reserves along the North Sea.
  • B. Voskuijl
    Voskuijl is a Dutch surname most notably associated with Bep Voskuijl, one of the helpers of Anne Frank and her family during their time in hiding.
  • C. Oosterstreek
    Oosterstreek is a small village in the municipality of Weststellingwerf in the Dutch province of Friesland.
  • D. Vollenhoven
    Vollenhoven is a Dutch surname most notably associated with philosopher D. H. Th. Vollenhoven, a key figure in Reformational philosophy.
  • E. Noordoewer
    Noordoewer is a small border town in southern Namibia on the Orange River, serving as a key road crossing point into South Africa.
  • 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_69fd280861fc81908c342fc229a526f3 completed May 8, 2026, 12:02 a.m.
Created at: April 10, 2026, 1:03 a.m.