Triple

T4448748
Position Surface form Disambiguated ID Type / Status
Subject Ossehoek E96354 entity
Predicate locatedInOrNear P40 FINISHED
Object Brouwersdam E19577 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: Brouwersdam | Statement: [Ossehoek, locatedInOrNear, Brouwersdam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brouwersdam
Context triple: [Ossehoek, locatedInOrNear, Brouwersdam]
  • A. Brouwersdam chosen
    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.
  • B. 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.
  • C. Werkendam
    Werkendam is a town in the Dutch province of North Brabant, known as a gateway to the Biesbosch National Park and its riverine landscapes.
  • D. Bemmelerwaard
    Bemmelerwaard is a riverine floodplain area in the Netherlands known for its natural landscapes and ecological value along the Waal.
  • E. Woudenberg
    Woudenberg is a small Dutch municipality and town located in the central Netherlands.
  • 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_69b345415ba481908df738e7174448ba completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b355d45b748190b09b7067fc6279b0 completed March 13, 2026, 12:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69bd6f7bfd4c8190adf670a5a11c8182 completed March 20, 2026, 4:02 p.m.
Created at: March 12, 2026, 11:32 p.m.