Triple

T17645305
Position Surface form Disambiguated ID Type / Status
Subject Rivierenland E429339 entity
Predicate contains P35 FINISHED
Object Neder-Betuwe 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: Neder-Betuwe | Statement: [Rivierenland, contains, Neder-Betuwe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neder-Betuwe
Context triple: [Rivierenland, contains, Neder-Betuwe]
  • A. Neder-Betuwe chosen
    Neder-Betuwe is a municipality in the Dutch province of Gelderland, known for its rural landscape, fruit cultivation, and location along the rivers Waal and Rhine.
  • B. West Betuwe
    West Betuwe is a municipality in the Dutch province of Gelderland, known for its rural landscape, historic villages, and location along major rivers in the central Netherlands.
  • C. Betuwe
    Betuwe is a fertile riverine region in the Dutch province of Gelderland, renowned for its extensive fruit orchards and scenic landscapes between the Rhine and Waal rivers.
  • D. Oosterstreek
    Oosterstreek is a small village in the municipality of Weststellingwerf in the Dutch province of Friesland.
  • E. Nederwaardse Boezem
    Nederwaardse Boezem is a Dutch polder waterway and drainage basin in the province of South Holland, known for its role in regional water management near the Lek River.
  • 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_69d889e2c2608190b762e76d9b2262f1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46e382ba88190af19d0e3b8c8cadd completed April 19, 2026, 5:55 a.m.
Created at: April 10, 2026, 6:04 a.m.