Triple

T17822293
Position Surface form Disambiguated ID Type / Status
Subject Jagst E445014 entity
Predicate hasLanguageVariantName P15 FINISHED
Object Jagst (German) 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: Jagst (German) | Statement: [Jagst, hasLanguageVariantName, Jagst (German)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jagst (German)
Context triple: [Jagst, hasLanguageVariantName, Jagst (German)]
  • A. Jagst chosen
    The Jagst is a river in Baden-Württemberg, Germany, known as one of the major right-bank tributaries of the Neckar and flowing through a largely rural, scenic landscape.
  • B. Jagsttal
    Jagsttal is the scenic valley region in southwestern Germany shaped by the course of the Jagst River, known for its rural landscapes and historic towns.
  • C. Lauter River
    The Lauter River is a small river in northeastern France and southwestern Germany that flows through the town of Wissembourg before joining the Rhine.
  • D. Hase River
    The Hase River is a river in northwestern Germany that flows through Lower Saxony and North Rhine-Westphalia before joining the Ems River.
  • E. Örtze River
    The Örtze River is a river in Lower Saxony, Germany, known for flowing through the Lüneburg Heath before joining the Aller.
  • 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_69d8b9f0de78819099395b14db75a8a6 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48911b660819097fc7ea94665a02a completed April 19, 2026, 7:49 a.m.
Created at: April 10, 2026, 10:15 a.m.