Triple

T15757596
Position Surface form Disambiguated ID Type / Status
Subject Innerste E382006 entity
Predicate hasTributary P415 FINISHED
Object Riehe E389216 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: Riehe | Statement: [Innerste, hasTributary, Riehe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Riehe
Context triple: [Innerste, hasTributary, Riehe]
  • A. Riehe chosen
    Riehe is a small river in Lower Saxony, Germany, known as one of the tributaries feeding into the Innerste.
  • B. Riedlingen
    Riedlingen is a small historic town in the state of Baden-Württemberg in southern Germany, known for its well-preserved medieval old town on the Danube River.
  • C. Rüthen
    Rüthen is a small historic town in North Rhine-Westphalia, Germany, known for its medieval architecture and location in the scenic Sauerland region.
  • D. Schönaich
    Schönaich is a municipality in the German state of Baden-Württemberg, known for its local community life and international town twinning partnerships.
  • E. Vaterstetten
    Vaterstetten is a municipality in the district of Ebersberg near Munich in Bavaria, Germany, known as a residential suburb with strong transport links to the Bavarian capital.
  • 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_69d86d9e6b44819085d1f6a969ecb74c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e050b1ff4881909d5240d1d30f5c8b completed April 16, 2026, 3 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffcf0bc4e88190be83324776b26df9 completed May 10, 2026, 12:19 a.m.
Created at: April 10, 2026, 4:47 a.m.