Triple

T4485405
Position Surface form Disambiguated ID Type / Status
Subject Roth (river) E107223 entity
Predicate hasMouthLocation P1008 FINISHED
Object Rednitz at Roth (town) E19589 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: Rednitz at Roth (town) | Statement: [Roth (river), hasMouthLocation, Rednitz at Roth (town)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rednitz at Roth (town)
Context triple: [Roth (river), hasMouthLocation, Rednitz at Roth (town)]
  • A. Roth bei Nürnberg (Austria)
    Roth bei Nürnberg (Austria) is an Austrian town that is officially twinned with the German town of Roth in Bavaria.
  • B. Rednitz chosen
    The Rednitz is a river in Bavaria, Germany, that flows through cities such as Fürth and joins with the Pegnitz to form the Regnitz.
  • C. Röthenbach
    Röthenbach is a station in Nuremberg, Germany that serves as a terminus on the city’s U-Bahn rapid transit network.
  • D. Ronsdorf
    Ronsdorf is a district of the German city of Wuppertal in North Rhine-Westphalia, historically known as an independent town in the Bergisches Land region.
  • E. district of Roth
    The district of Roth is a rural administrative district in Middle Franconia, Bavaria, Germany, known for its mix of small towns, forests, and river landscapes.
  • 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_69bd43f84f788190a1383579c4a595be completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd52a758f48190b6b59ca0d9207c2a completed March 20, 2026, 1:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69bd56b2f4e08190812d3909cc327b06 completed March 20, 2026, 2:16 p.m.
Created at: March 20, 2026, 12:59 p.m.