Triple

T14918906
Position Surface form Disambiguated ID Type / Status
Subject Rhine bridge at Arnhem E371456 entity
Predicate crosses P416 FINISHED
Object Nederrijn 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: Nederrijn | Statement: [Rhine bridge at Arnhem, crosses, Nederrijn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nederrijn
Context triple: [Rhine bridge at Arnhem, crosses, Nederrijn]
  • 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. Rijn
    Rijn is the Dutch name for the major European river known in English as the Rhine.
  • 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. Drentsche Aa
    Drentsche Aa is a small, meandering river in the Dutch province of Drenthe, renowned for its well-preserved natural landscape and surrounding national park.
  • E. Oude Rijn
    Oude Rijn is a river in the western Netherlands that forms one of the main northern distributaries of the Rhine, flowing through towns such as Leiden before reaching the North Sea.
  • 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_69d85cc7ea3481908228b5acb7d06f12 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded62f76bc81909ebc8899096cd1a0 completed April 15, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69feae048fa08190ba5719ca9868b50d completed May 9, 2026, 3:46 a.m.
Created at: April 10, 2026, 2:33 a.m.