Triple

T3002729
Position Surface form Disambiguated ID Type / Status
Subject Rijn E81826 entity
Predicate hasPart P35 FINISHED
Object Neder-Rijn E92543 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: Neder-Rijn | Statement: [Rijn, hasPart, Neder-Rijn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neder-Rijn
Context triple: [Rijn, hasPart, Neder-Rijn]
  • A. Nederrijn chosen
    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.
  • 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. Hollandsche IJssel
    Hollandsche IJssel is a river in the western Netherlands that flows through the provinces of South Holland and Utrecht and plays a role in regional water management and flood control.
  • 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_69ad8b1c4de88190a83b7cefaa1f2842 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9a1371c481909e214234afed1a65 completed March 8, 2026, 3:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b12e4f02248190890eb3944299bd15 completed March 11, 2026, 8:56 a.m.
Created at: March 8, 2026, 2:59 p.m.