Triple

T857660
Position Surface form Disambiguated ID Type / Status
Subject Delta Works E18527 entity
Predicate hasPart P35 FINISHED
Object Philipsdam E40807 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: Philipsdam | Statement: [Delta Works, hasPart, Philipsdam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Philipsdam
Context triple: [Delta Works, hasPart, Philipsdam]
  • A. Philipsdam chosen
    Philipsdam is a major Dutch dam and storm surge barrier that forms part of the Delta Works, protecting the Rhine–Meuse–Scheldt delta from flooding.
  • B. Sluis
    Sluis is a historic municipality and town in the southwestern Dutch province of Zeeland, near the Belgian border.
  • C. Grevelingendam
    Grevelingendam is a major dam in the southwestern Netherlands that forms part of the Delta Works, protecting the Rhine–Meuse–Scheldt delta from flooding while separating the Grevelingenmeer from the North Sea.
  • D. Maassluis
    Maassluis is a historic port town in the province of South Holland in the Netherlands, situated along the Nieuwe Waterweg west of Rotterdam.
  • E. Brouwersdam
    Brouwersdam is a major Dutch dam and causeway in the Rhine–Meuse–Scheldt delta, built as part of the Delta Works to protect the Netherlands from North Sea flooding while supporting road traffic and water management.
  • 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_69a4938bdd3c8190a954a3c11844d9cf completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac4d47508190b48d944aa2d881bf completed March 1, 2026, 9:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad0e56e7fc8190a81cbd97e20fd0e6 completed March 8, 2026, 5:51 a.m.
Created at: March 1, 2026, 7:39 p.m.