Triple

T3789366
Position Surface form Disambiguated ID Type / Status
Subject Nieuw-Beijerland E89606 entity
Predicate locatedIn P40 FINISHED
Object Hoeksche Waard E598686 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: Hoeksche Waard | Statement: [Nieuw-Beijerland, locatedIn, Hoeksche Waard]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hoeksche Waard
Context triple: [Nieuw-Beijerland, locatedIn, Hoeksche Waard]
  • A. Hoeksche Waard chosen
    Hoeksche Waard is a rural island and municipality in South Holland, Netherlands, known for its agricultural landscape and small towns.
  • B. Hulst
    Hulst is a historic fortified town and municipality in the Dutch province of Zeeland, near the border with Belgium.
  • C. Valkenswaard
    Valkenswaard is a town in the southern Netherlands known for its strong equestrian culture and international show jumping events.
  • D. Noorderhaaks
    Noorderhaaks is a small, uninhabited sandbar island off the Dutch coast, forming the westernmost part of the West Frisian Islands archipelago.
  • E. Zwijndrecht
    Zwijndrecht is a Dutch town and municipality located in the western Netherlands, known for its position along the rivers near the city of Dordrecht.
  • 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_69aed9597d6881909b6ee3b9de859223 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aee76570b481909c26d47a3251b180 completed March 9, 2026, 3:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69d065a63f8c8190a50f814fb70e0e31 completed April 4, 2026, 1:13 a.m.
Created at: March 9, 2026, 3:15 p.m.