Triple

T16382545
Position Surface form Disambiguated ID Type / Status
Subject Amerongen weir E397843 entity
Predicate watercourse P415 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: [Amerongen weir, watercourse, Nederrijn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nederrijn
Context triple: [Amerongen weir, watercourse, 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. Nieuwe Rijn
    Nieuwe Rijn is a canal and street in the historic center of Leiden, Netherlands, known for its picturesque quays, markets, and traditional Dutch canal-side architecture.
  • D. 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.
  • E. 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.
  • 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_69d87f2880b48190ae1a9673a3bbef80 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e319ddcef08190a2081855b5cf6762 completed April 18, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a007d9c8de4819093ae3901cf0c8805 completed May 10, 2026, 12:44 p.m.
Created at: April 10, 2026, 5:08 a.m.