Triple

T7994733
Position Surface form Disambiguated ID Type / Status
Subject Aurach E186094 entity
Predicate partOf P40 FINISHED
Object Regnitz river system E124915 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: Regnitz river system | Statement: [Aurach, partOf, Regnitz river system]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Regnitz river system
Context triple: [Aurach, partOf, Regnitz river system]
  • A. Regnitz chosen
    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.
  • B. Würm River
    The Würm River is a small river in Bavaria, Germany, known for flowing north from Lake Starnberg through towns such as Gauting and Starnberg before joining the Amper River.
  • C. Schwabach River
    The Schwabach River is a small river in Bavaria, Germany, that flows through the town of Schwabach before joining the Rednitz River.
  • D. Rednitz river basin
    The Rednitz river basin is the drainage area in Franconia, Germany, encompassing the Rednitz River and its tributaries, including the Roth.
  • E. Wiese River
    The Wiese River is a tributary of the Rhine flowing through parts of Germany and Switzerland, including the municipality of Riehen near Basel.
  • 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_69ca829c6c308190ab05b43d234c52b2 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3c73ba388190bcedc29fbdd22f3c completed March 31, 2026, 3:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc568ac4e88190b63b4d57c3bd3205 completed March 31, 2026, 11:19 p.m.
Created at: March 30, 2026, 5:17 p.m.