Triple

T5648210
Position Surface form Disambiguated ID Type / Status
Subject Volkerak E124435 entity
Predicate separatedFrom P243 FINISHED
Object Haringvliet E144759 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: Haringvliet | Statement: [Volkerak, separatedFrom, Haringvliet]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Haringvliet
Context triple: [Volkerak, separatedFrom, Haringvliet]
  • A. Haringvliet chosen
    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.
  • B. Haringvlietdam
    Haringvlietdam is a major Dutch storm surge barrier and dam complex that regulates water flow and protects the southwestern Netherlands from flooding as part of the Delta Works.
  • C. Reitdiep
    Reitdiep is a historic canalized river in the province of Groningen in the Netherlands, known for its scenic landscapes and colorful waterfront houses near the city of Groningen.
  • D. Eendracht
    Eendracht was a prominent 17th-century Dutch warship that served as the flagship of the Dutch fleet during major naval engagements of the Anglo-Dutch Wars.
  • E. Eendracht
    Eendracht is a waterway in the southwestern Netherlands that forms part of the main shipping route between the Scheldt and Rhine river systems.
  • 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_69c00825df388190a58742fa9b1aa33d completed March 22, 2026, 3:17 p.m.
NER Named-entity recognition batch_69c022d1534c8190ac4828e44300fb91 completed March 22, 2026, 5:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0bf7396c48190a4de4958e2ad4301 completed March 23, 2026, 4:20 a.m.
Created at: March 22, 2026, 3:42 p.m.