Triple

T3002755
Position Surface form Disambiguated ID Type / Status
Subject Rijn E81826 entity
Predicate FrenchName P744 FINISHED
Object Rhin E81445 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: Rhin | Statement: [Rijn, FrenchName, Rhin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rhin
Context triple: [Rijn, FrenchName, Rhin]
  • A. Rhin chosen
    Rhin is the French name for the Rhine, one of Europe’s major rivers flowing through countries such as Switzerland, Germany, and the Netherlands.
  • B. Rhin
    The Rhin is a small river in northeastern Germany that flows through Brandenburg and serves as a tributary within the Havel river system.
  • C. Rheinbund
    The Rheinbund, or Confederation of the Rhine, was a coalition of German states organized under the influence of Napoleon in the early 19th century that effectively ended the Holy Roman Empire and served as a French client confederation.
  • D. Nahe
    Nahe is a renowned German wine region, particularly celebrated for producing high-quality Riesling wines with diverse styles due to its varied soils and microclimates.
  • E. 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.
  • 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_69ad8b1c4de88190a83b7cefaa1f2842 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9a1371c481909e214234afed1a65 completed March 8, 2026, 3:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b12e4f02248190890eb3944299bd15 completed March 11, 2026, 8:56 a.m.
Created at: March 8, 2026, 2:59 p.m.