Triple

T17157368
Position Surface form Disambiguated ID Type / Status
Subject Wermelskirchen E416377 entity
Predicate hasNearbyWaterBody P1489 FINISHED
Object Wupper River NE NERFINISHED

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: Wupper River | Statement: [Wermelskirchen, hasNearbyWaterBody, Wupper River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wupper River
Context triple: [Wermelskirchen, hasNearbyWaterBody, Wupper River]
  • A. Wupper chosen
    The Wupper is a river in North Rhine-Westphalia, Germany, known for flowing through the industrial city of Wuppertal and its surrounding region.
  • B. Schwalm River
    The Schwalm River is a waterway in the German state of Hesse that lends its name to the surrounding Schwalm-Eder region.
  • C. Regnitz
    The Regnitz is a river in the German state of Bavaria that flows through cities such as Erlangen and Bamberg before joining the Main River.
  • D. Blies
    The Blies is a river in western Germany and northeastern France that flows through the Saarland region before joining the Saar River.
  • E. Fulda River
    The Fulda River is a major river in central Germany that flows through the state of Hesse and joins the Werra River at Hann. Münden to form the Weser.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d886d279c081909f8ff1f743ddeb69 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3f40bf9ec8190b16372bcd091db9b completed April 18, 2026, 9:13 p.m.
Created at: April 10, 2026, 5:37 a.m.