Triple

T3045944
Position Surface form Disambiguated ID Type / Status
Subject Snelbinder (rail and cycle bridge) E83446 entity
Predicate crosses P416 FINISHED
Object River Waal E328453 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 Waal | Statement: [Snelbinder (rail and cycle bridge), crosses, River Waal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Waal
Context triple: [Snelbinder (rail and cycle bridge), crosses, River Waal]
  • A. River Waal chosen
    River Waal is a major distributary branch of the Rhine in the Netherlands, serving as an important waterway for transport and trade.
  • B. 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.
  • C. Gelderse IJssel
    Gelderse IJssel is the Dutch name for the branch of the River IJssel that flows through the province of Gelderland in the Netherlands.
  • 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. Amstel River
    The Amstel River is a historic waterway in the Netherlands that flows through and gives its name to the city 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_69ad8b24924c8190a9bb6f61d519e4ae completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9bab541c8190a17aca26b3dcfae7 completed March 8, 2026, 3:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69b224b717e081909462645d78b33cc9 completed March 12, 2026, 2:28 a.m.
Created at: March 8, 2026, 3:01 p.m.