Triple

T14186659
Position Surface form Disambiguated ID Type / Status
Subject Binnenmaas E351594 entity
Predicate mergedWith P77 FINISHED
Object Oud-Beijerland E90858 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: Oud-Beijerland | Statement: [Binnenmaas, mergedWith, Oud-Beijerland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oud-Beijerland
Context triple: [Binnenmaas, mergedWith, Oud-Beijerland]
  • A. Oud-Beijerland chosen
    Oud-Beijerland is a town in the western Netherlands known as one of the main population centers in the Hoeksche Waard region.
  • B. Zuid-Beijerland
    Zuid-Beijerland is a village in the western Netherlands, located in the province of South Holland and known for its rural character within the Hoeksche Waard region.
  • C. Hoeksche Waard
    Hoeksche Waard is a rural island and municipality in South Holland, Netherlands, known for its agricultural landscape and small towns.
  • D. Hoeksche Waard region
    The Hoeksche Waard region is a rural island area in South Holland, Netherlands, characterized by its agricultural landscape, historic villages, and network of polders and dikes.
  • E. Albrandswaard
    Albrandswaard is a municipality in the western Netherlands, situated just south of Rotterdam in the province of South Holland.
  • 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_69fff288ba908190a36c4784331d1e60 completed May 10, 2026, 2:50 a.m.
Created at: April 10, 2026, 1:03 a.m.