Triple

T1401655
Position Surface form Disambiguated ID Type / Status
Subject Kostverlorenvaart E31597 entity
Predicate connectsWith P37 FINISHED
Object River Amstel E4253 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: River Amstel | Statement: [Kostverlorenvaart, connectsWith, River Amstel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Amstel
Context triple: [Kostverlorenvaart, connectsWith, River Amstel]
  • A. Amstel River chosen
    The Amstel River is a historic waterway in the Netherlands that flows through and gives its name to the city of Amsterdam.
  • B. Waal
    The Waal is a major distributary branch of the Rhine River in the Netherlands, serving as an important waterway for shipping and part of the country’s main river system.
  • C. Vaartsche Rijn
    Vaartsche Rijn is a historic canal in the Dutch province of Utrecht that connects the city of Utrecht with the Lower Rhine and forms part of its inland waterway network.
  • D. Oude Maas
    The Oude Maas is a major distributary river in the western Netherlands that forms part of the complex Rhine–Meuse–Scheldt delta system.
  • E. Ouder-Amstel
    Ouder-Amstel is a municipality in the province of North Holland in the Netherlands, located just southeast of Amsterdam.
  • 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_69a49918e1f88190ba610f9dc8114578 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c39da20c8190b9c82cc4ad747c66 completed March 1, 2026, 10:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69adfb8a58ec81908b2bb5c27283bafa completed March 8, 2026, 10:43 p.m.
Created at: March 1, 2026, 7:59 p.m.