Triple

T2256718
Position Surface form Disambiguated ID Type / Status
Subject Haut-Rhin E49743 entity
Predicate borderRiver P224 FINISHED
Object Rhine E13461 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: Rhine | Statement: [Haut-Rhin, borderRiver, Rhine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rhine
Context triple: [Haut-Rhin, borderRiver, Rhine]
  • A. Rhine chosen
    The Rhine is one of Europe's most important rivers, historically serving as a vital trade route and cultural boundary from the Alps through Germany to the North Sea.
  • B. 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.
  • C. Rhens
    Rhens is a historic town on the Rhine River in western Germany, known for its medieval role as a meeting place of the prince-electors of the Holy Roman Empire.
  • D. Weser
    The Weser is a major river in northwestern Germany that flows through several federal states before emptying into the North Sea.
  • E. Neckar
    The Neckar is a significant river in southwestern Germany that flows through cities like Stuttgart and Heidelberg before joining the Rhine.
  • 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_69a88aaa9250819095e127d0d77e8a32 completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc1570dc88190bb2b17ed4c25dbb5 completed March 7, 2026, 6:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69b2031a55148190a1b96af35d109259 completed March 12, 2026, 12:04 a.m.
Created at: March 4, 2026, 7:47 p.m.