Triple

T890643
Position Surface form Disambiguated ID Type / Status
Subject Haringvlietdam E19229 entity
Predicate nearbyCity P350 FINISHED
Object Stellendam E105216 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: Stellendam | Statement: [Haringvlietdam, nearbyCity, Stellendam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stellendam
Context triple: [Haringvlietdam, nearbyCity, Stellendam]
  • A. Stellendam chosen
    Stellendam is a small village in the western Netherlands, located on the island of Goeree-Overflakkee and known for its fishing harbor and proximity to the North Sea.
  • B. Maassluis
    Maassluis is a historic port town in the province of South Holland in the Netherlands, situated along the Nieuwe Waterweg west of Rotterdam.
  • C. Scheveningen
    Scheveningen is a popular seaside resort district of The Hague in the Netherlands, known for its long sandy beach, pier, and promenade along the North Sea coast.
  • D. Delfzijl
    Delfzijl is a port town in the northeast of the Netherlands, known for its maritime industry and location on the Ems estuary near the German border.
  • E. Terneuzen port
    Terneuzen port is a major Dutch seaport and industrial hub on the Western Scheldt, known for its role in maritime trade and access to the Ghent–Terneuzen Canal.
  • 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_69a4939d37188190848be3d426ebc9ae completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ad0086a081908c47c285896a1f3c completed March 1, 2026, 9:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac4282ea908190817857231b98f5b4 completed March 7, 2026, 3:21 p.m.
Created at: March 1, 2026, 7:39 p.m.