Triple

T20317752
Position Surface form Disambiguated ID Type / Status
Subject Maassluis railway station E510421 entity
Predicate near P350 FINISHED
Object Nieuwe Waterweg 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: Nieuwe Waterweg | Statement: [Maassluis railway station, near, Nieuwe Waterweg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nieuwe Waterweg
Context triple: [Maassluis railway station, near, Nieuwe Waterweg]
  • A. Nieuwe Waterweg chosen
    Nieuwe Waterweg is a major artificial ship canal in the Netherlands that provides a direct deep-water connection between the North Sea and the port of Rotterdam.
  • B. Drecht
    Drecht is a lesser-known Dutch river whose waters help form the Amstel through their confluence.
  • C. Drentsche Hoofdvaart
    Drentsche Hoofdvaart is a historic canal in the Dutch province of Drenthe that serves as an important waterway for transport and recreation.
  • D. Hoogeveense Vaart
    Hoogeveense Vaart is a canal in the Dutch province of Drenthe that serves as an important waterway for transport and drainage in the region.
  • E. Rijnmond
    Rijnmond is a region in the western Netherlands centered around the port city of Rotterdam and the Rhine–Meuse river delta.
  • 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_69e0b4c7491c8190961113c4283b10b0 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e67788ca3c8190a3496fd54a5870d6 completed April 20, 2026, 6:59 p.m.
Created at: April 16, 2026, 11:19 a.m.