Triple

T4658174
Position Surface form Disambiguated ID Type / Status
Subject Cleves E102459 entity
Predicate region P40 FINISHED
Object Niederrhein E360139 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: Niederrhein | Statement: [Cleves, region, Niederrhein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Niederrhein
Context triple: [Cleves, region, Niederrhein]
  • A. North Rhine
    North Rhine is a historical region in western Germany that forms part of the larger Rhineland area along the Rhine River.
  • B. Mittelrhein
    Mittelrhein is a scenic section of Germany’s Middle Rhine Valley, renowned for its steep vineyards, medieval castles, and picturesque riverside towns.
  • C. Lower Rhine chosen
    The Lower Rhine is the downstream section of the Rhine River flowing from roughly Bonn through Germany and the Netherlands to the North Sea, known for its dense population, industry, and historical river landscapes.
  • D. Lippe
    The Lippe is a river in western Germany that flows through North Rhine-Westphalia and is a right-bank tributary of the Rhine.
  • E. Lippe
    Lippe is a historical region in northwestern Germany that once formed a small principality and later a Free State within the German Reich.
  • 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_69bd43d823288190952279faa0d1d066 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd63271a548190bd9662b69a45d9a5 completed March 20, 2026, 3:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69bed8fed2208190a3e340190356e67f completed March 21, 2026, 5:44 p.m.
Created at: March 20, 2026, 1:15 p.m.