Triple

T6952515
Position Surface form Disambiguated ID Type / Status
Subject Overtoomsesluisbrug E160961 entity
Predicate crosses P416 FINISHED
Object Kostverlorenvaart E31597 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: Kostverlorenvaart | Statement: [Overtoomsesluisbrug, crosses, Kostverlorenvaart]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kostverlorenvaart
Context triple: [Overtoomsesluisbrug, crosses, Kostverlorenvaart]
  • A. Kostverlorenvaart chosen
    Kostverlorenvaart is a canal in Amsterdam that connects the city's western waterways with the River Amstel and the IJ.
  • B. Leidsevaart
    Leidsevaart is a historic canal in the Netherlands that runs between Haarlem and Leiden and was once an important route for passenger boats and trade.
  • 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. Haringvliet
    Haringvliet is a former estuary in the western Netherlands that now functions as a controlled waterway and nature area connecting the Rhine-Meuse river system to the North Sea.
  • 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_69c68850419081909fb426b8f5a304c7 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dab18d648190a2f238fce3e59365 completed March 27, 2026, 7:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7942eeb288190acad3bf999a6ea2e completed March 28, 2026, 8:41 a.m.
Created at: March 27, 2026, 2:29 p.m.