Triple

T19636417
Position Surface form Disambiguated ID Type / Status
Subject Haringvliet estuary E471408 entity
Predicate nearCity P350 FINISHED
Object Stellendam NE NERFINISHED

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: [Haringvliet estuary, nearCity, Stellendam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stellendam
Context triple: [Haringvliet estuary, nearCity, 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. Volendam
    Volendam is a traditional Dutch fishing village and popular tourist destination known for its historic harbor, wooden houses, and preserved local costumes.
  • C. Onderdendam
    Onderdendam is a small historic village in the Dutch province of Groningen, known for its canals, bridges, and traditional architecture.
  • D. Zaandam
    Zaandam is a city in the North Holland province of the Netherlands, known for its historic windmills, traditional wooden houses, and proximity to Amsterdam.
  • E. Stolwijk
    Stolwijk is a village in the Dutch province of South Holland, known for its traditional rural character and location in the Krimpenerwaard polder landscape.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e511f28481909f4bc3ea9191e54a completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e641070528819085663c439f50148e completed April 20, 2026, 3:06 p.m.
Created at: April 10, 2026, 1:44 p.m.