Triple

T22530291
Position Surface form Disambiguated ID Type / Status
Subject Roth district E557013 entity
Predicate hasRiver P165 FINISHED
Object Schwarzach 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: Schwarzach | Statement: [Roth district, hasRiver, Schwarzach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schwarzach
Context triple: [Roth district, hasRiver, Schwarzach]
  • A. Schwarzach
    Schwarzach is a municipality in the Austrian state of Vorarlberg, located in the district of Bregenz.
  • B. Schwarzach
    Schwarzach is a municipality in the Straubing-Bogen district of Lower Bavaria, Germany, known for its rural setting in the Bavarian Forest region.
  • C. Schwarzach chosen
    Schwarzach is a river in Bavaria, Germany, known as a tributary of the Rednitz.
  • D. Schwarzach am Main
    Schwarzach am Main is a small municipality in the Lower Franconia region of Bavaria, Germany, situated along the Main River and known for its winegrowing and historic monastery.
  • E. Wolfratshausen
    Wolfratshausen is a Bavarian town in southern Germany known for its historic old town, riverside setting on the Loisach and Isar, and proximity to Munich and the Alps.
  • 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_69e11e57483c8190b0887c4f8ff26446 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15ed6734881908abbbee477dfab98 completed April 29, 2026, 1:28 a.m.
Created at: April 16, 2026, 8:51 p.m.