Triple

T18240945
Position Surface form Disambiguated ID Type / Status
Subject Bad Kreuznach E436807 entity
Predicate locatedOnRiver P165 FINISHED
Object Nahe 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: Nahe | Statement: [Bad Kreuznach, locatedOnRiver, Nahe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nahe
Context triple: [Bad Kreuznach, locatedOnRiver, Nahe]
  • A. Nahe chosen
    Nahe is a river in western Germany, known for flowing through the Nahe wine region before joining the Rhine.
  • B. Nahe
    Nahe is a renowned German wine region, particularly celebrated for producing high-quality Riesling wines with diverse styles due to its varied soils and microclimates.
  • C. Ruwer
    Ruwer is a small wine-growing region in Germany’s Mosel area, noted for its cool climate and production of light, crisp white wines.
  • D. Neckertal
    Neckertal is a municipality in the Swiss canton of St. Gallen, known for its rural landscape and location within the Toggenburg region.
  • E. Neesen
    Neesen is a former locality in North Rhine-Westphalia, Germany, that was incorporated into the town of Porta Westfalica.
  • 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_69d8b91104e08190a8241f7d260a5162 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4f7e287548190b666a990e5b168b0 completed April 19, 2026, 3:42 p.m.
Created at: April 10, 2026, 10:33 a.m.