Triple

T3107788
Position Surface form Disambiguated ID Type / Status
Subject Vaartsche Rijn E64874 entity
Predicate hasNameInLanguage P15 FINISHED
Object nl: Vaartsche Rijn E64874 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: nl: Vaartsche Rijn | Statement: [Vaartsche Rijn, hasNameInLanguage, nl: Vaartsche Rijn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: nl: Vaartsche Rijn
Context triple: [Vaartsche Rijn, hasNameInLanguage, nl: Vaartsche Rijn]
  • A. Vaartsche Rijn chosen
    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.
  • B. Nederrijn
    The Nederrijn is a major distributary branch of the Rhine River in the Netherlands, flowing through cities such as Arnhem and forming an important part of the Dutch river system.
  • C. Rijn
    Rijn is the Dutch name for the major European river known in English as the Rhine.
  • D. 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.
  • E. Kostverlorenvaart
    Kostverlorenvaart is a canal in Amsterdam that connects the city's western waterways with the River Amstel and the IJ.
  • 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_69ad857eeaf48190b34ebfdaa7a264cf completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada29eacc88190a19c5ca8e53e3dca completed March 8, 2026, 4:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69b2038c89248190b880108c82ad35b1 completed March 12, 2026, 12:06 a.m.
Created at: March 8, 2026, 3:04 p.m.