Triple

T6835330
Position Surface form Disambiguated ID Type / Status
Subject Leidsevaart E157434 entity
Predicate hasDutchName P744 FINISHED
Object Leidsevaart E157434 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: Leidsevaart | Statement: [Leidsevaart, hasDutchName, Leidsevaart]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leidsevaart
Context triple: [Leidsevaart, hasDutchName, Leidsevaart]
  • A. Leidsevaart chosen
    Leidsevaart is a historic canal in the Netherlands that runs between Haarlem and Leiden and was once an important route for passenger boats and trade.
  • B. Kostverlorenvaart
    Kostverlorenvaart is a canal in Amsterdam that connects the city's western waterways with the River Amstel and the IJ.
  • C. De Rotterdam
    De Rotterdam is a massive mixed-use high-rise complex in Rotterdam, Netherlands, designed by the architecture firm OMA and known for its stacked, shifting tower volumes along the Maas River.
  • D. Muiderkring
    Muiderkring was a 17th-century Dutch literary and artistic circle centered around P.C. Hooft and other prominent writers and intellectuals who gathered at Muiden Castle.
  • E. Sluis
    Sluis is a historic municipality and town in the southwestern Dutch province of Zeeland, near the Belgian border.
  • 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_69c6882c53608190b99aebef079b23bd completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d67a9ff88190b0d86331b3ea06aa completed March 27, 2026, 7:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69c72fb02e0c8190ae1514875e03208a completed March 28, 2026, 1:32 a.m.
Created at: March 27, 2026, 2:19 p.m.