Triple

T21389722
Position Surface form Disambiguated ID Type / Status
Subject Reuss-Ebersdorf E527608 entity
Predicate mergedInto P77 FINISHED
Object Reuss-Schleiz 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: Reuss-Schleiz | Statement: [Reuss-Ebersdorf, mergedInto, Reuss-Schleiz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Reuss-Schleiz
Context triple: [Reuss-Ebersdorf, mergedInto, Reuss-Schleiz]
  • A. Reuss-Schleiz chosen
    Reuss-Schleiz was a small historical German principality ruled by a branch of the House of Reuss within the Holy Roman Empire and later the German Confederation.
  • B. Rüdnitz
    Rüdnitz is a small municipality in the Barnim district of the federal state of Brandenburg in northeastern Germany.
  • C. Schwarzbach
    Schwarzbach is a river in southwestern Germany that flows through the town of Zweibrücken in the state of Rhineland-Palatinate.
  • D. 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.
  • E. Fränkische Saale
    The Fränkische Saale is a river in northern Bavaria, Germany, known for flowing through the Franconian wine region and eventually joining the Main River.
  • 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_69e0b51ff3748190935c0a513c62a12b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b0f8ae288190b43df9fe2841a822 completed April 22, 2026, 11:28 a.m.
Created at: April 16, 2026, 5:13 p.m.