Triple

T1475283
Position Surface form Disambiguated ID Type / Status
Subject Wittenberg E30826 entity
Predicate locatedOnRiver P165 FINISHED
Object Elbe River E16410 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: Elbe River | Statement: [Wittenberg, locatedOnRiver, Elbe River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elbe River
Context triple: [Wittenberg, locatedOnRiver, Elbe River]
  • A. Elbe chosen
    The Elbe is one of Central Europe's major rivers, flowing from the Czech Republic through Germany to the North Sea and serving as an important waterway for transport, industry, and agriculture.
  • B. Saale
    The Saale is a major river in central Germany that flows through the states of Thuringia, Saxony-Anhalt, and Bavaria before joining the Elbe.
  • C. Weser
    The Weser is a major river in northwestern Germany that flows through several federal states before emptying into the North Sea.
  • D. Oder River
    The Oder River is a major Central European river that flows through the Czech Republic, Poland, and along the Polish–German border before emptying into the Baltic Sea.
  • E. 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.
  • 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_69a498fe55a88190ab7f9e40ace88e49 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c602387c8190b97a20c8e05e3d16 completed March 1, 2026, 11:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69ae5162c078819085c7fbc11f679d56 completed March 9, 2026, 4:49 a.m.
Created at: March 1, 2026, 8:11 p.m.