Triple

T16278983
Position Surface form Disambiguated ID Type / Status
Subject Renkum E395212 entity
Predicate hasBorderWith P224 FINISHED
Object Overbetuwe E823098 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: Overbetuwe | Statement: [Renkum, hasBorderWith, Overbetuwe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Overbetuwe
Context triple: [Renkum, hasBorderWith, Overbetuwe]
  • A. Overbetuwe chosen
    Overbetuwe is a municipality in the Dutch province of Gelderland, located in the Betuwe region and known for its rural landscape and fruit cultivation.
  • B. 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.
  • C. Humbeek
    Humbeek is a village in the Flemish Brabant province of Belgium, known as one of the constituent towns of the municipality of Grimbergen.
  • D. Bezuidenhout
    Bezuidenhout is a neighborhood in The Hague, Netherlands, known for its residential character and proximity to major government and business districts.
  • E. Uithoorn
    Uithoorn is a town and municipality in the province of North Holland in the Netherlands, situated along the Amstel River.
  • 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_69d87f22c7248190a54c949738441e2e completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e24610908c8190921e507dcb4d8250 completed April 17, 2026, 2:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a007d9a8d7481908c7bc4711ddacc13 completed May 10, 2026, 12:44 p.m.
Created at: April 10, 2026, 5:05 a.m.