Triple

T10071875
Position Surface form Disambiguated ID Type / Status
Subject Voorne-Putten E213647 entity
Predicate hasPart P35 FINISHED
Object Voorne E213647 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: Voorne | Statement: [Voorne-Putten, hasPart, Voorne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Voorne
Context triple: [Voorne-Putten, hasPart, Voorne]
  • A. Voorne aan Zee
    Voorne aan Zee is a municipality in the Dutch province of South Holland that includes the historic port town of Hellevoetsluis and other nearby communities on the island of Voorne.
  • B. Voorne-Putten chosen
    Voorne-Putten is an island and region in the province of South Holland in the Netherlands, known for its mix of coastal landscapes, nature reserves, and historic towns.
  • C. Sappemeer
    Sappemeer is a town in the province of Groningen in the northeastern Netherlands, historically known for its peat colonies and waterways.
  • D. Vechta
    Vechta is a town in Lower Saxony, Germany, known for its historical significance, university, and annual Stoppelmarkt fair.
  • E. Monnickendam
    Monnickendam is a historic fishing town in North Holland, Netherlands, known for its well-preserved old harbor and traditional Dutch architecture.
  • 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_69ca839add308190b57d53b4ec21f2d0 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdd01279388190b94c8def00425c78 completed April 2, 2026, 2:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d29aaa61308190b134b49a6c1c1131 completed April 5, 2026, 5:23 p.m.
Created at: March 30, 2026, 8:59 p.m.