Triple

T18274856
Position Surface form Disambiguated ID Type / Status
Subject Heidelberg Mountain Railway E437707 entity
Predicate locatedNear P294 FINISHED
Object Neckar River 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: Neckar River | Statement: [Heidelberg Mountain Railway, locatedNear, Neckar River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Neckar River
Context triple: [Heidelberg Mountain Railway, locatedNear, 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. River Iller
    The River Iller is a major river in southern Germany that flows through the Allgäu region and joins the Danube near Ulm.
  • D. 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.
  • E. 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.
  • 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_69d8b914530c8190b4474d862a2b2a1b completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50050d6688190b909a1c24e1dd3c9 completed April 19, 2026, 4:18 p.m.
Created at: April 10, 2026, 10:34 a.m.