Triple

T5519102
Position Surface form Disambiguated ID Type / Status
Subject Haringvliet E144759 entity
Predicate nearCity 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: [Haringvliet, nearCity, Stellendam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stellendam
Context triple: [Haringvliet, 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. 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.
  • D. Alblasserdam
    Alblasserdam is a town and municipality in the western Netherlands, situated along the Noord River and known for its proximity to the Kinderdijk windmills.
  • E. Brouwershaven
    Brouwershaven is a small historic town in the Dutch province of Zeeland, known for its maritime heritage and well-preserved old center.
  • 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_69c008f77ff88190b0cd50ca207295d1 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01f6eb604819092e9b2207dc741a9 completed March 22, 2026, 4:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69c027e57ed88190b2ff3245226851d1 completed March 22, 2026, 5:33 p.m.
Created at: March 22, 2026, 3:33 p.m.