Triple

T21166663
Position Surface form Disambiguated ID Type / Status
Subject Rotenburg an der Fulda E521581 entity
Predicate locatedOnRiver P165 FINISHED
Object Fulda River E662129 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: Fulda River | Statement: [Rotenburg an der Fulda, locatedOnRiver, Fulda River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fulda River
Context triple: [Rotenburg an der Fulda, locatedOnRiver, Fulda River]
  • A. Fulda River chosen
    The Fulda River is a major river in central Germany that flows through the state of Hesse and joins the Werra River at Hann. Münden to form the Weser.
  • B. Schwalm River
    The Schwalm River is a waterway in the German state of Hesse that lends its name to the surrounding Schwalm-Eder region.
  • C. Aschaff River
    The Aschaff River is a small river in Bavaria, Germany, that flows through the Spessart region before joining the Main River.
  • D. Wiese River
    The Wiese River is a tributary of the Rhine flowing through parts of Germany and Switzerland, including the municipality of Riehen near Basel.
  • E. Töss River
    The Töss River is a tributary of the Rhine in the canton of Zurich, Switzerland, known for flowing through the Töss Valley and past several towns including Winterthur.
  • 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_69e0b50e30748190b186824a206d39b9 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7270fce708190a5715b55b406dd4e completed April 21, 2026, 7:28 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0a735b9e5881909ec8672fd82c1068 completed May 18, 2026, 2:03 a.m.
Created at: April 16, 2026, 2:59 p.m.