Triple

T8950340
Position Surface form Disambiguated ID Type / Status
Subject Bad Cannstatt E213328 entity
Predicate locatedOn P40 FINISHED
Object Neckar River E79602 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: Neckar River | Statement: [Bad Cannstatt, locatedOn, Neckar River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neckar River
Context triple: [Bad Cannstatt, locatedOn, Neckar River]
  • A. Neckar chosen
    The Neckar is a significant river in southwestern Germany that flows through cities like Stuttgart and Heidelberg before joining the Rhine.
  • B. Kinzig
    The Kinzig is a river in southwestern Germany that flows through the Black Forest region before joining the Rhine.
  • C. High Rhine
    The High Rhine is a stretch of the Rhine River in Central Europe, flowing swiftly between Lake Constance and Basel and forming part of the border between Germany and Switzerland.
  • D. Würm River
    The Würm River is a small river in Bavaria, Germany, known for flowing north from Lake Starnberg through towns such as Gauting and Starnberg before joining the Amper River.
  • E. Regnitz
    The Regnitz is a river in the German state of Bavaria that flows through cities such as Erlangen and Bamberg before joining the Main River.
  • 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_69ca839843408190a39069a029a89f15 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc670c7244819084978922a9835bc9 completed April 1, 2026, 12:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2693f054081909fe58a252bd76226 completed April 5, 2026, 1:53 p.m.
Created at: March 30, 2026, 6:59 p.m.