Triple

T15187872
Position Surface form Disambiguated ID Type / Status
Subject Königsstuhl von Rhens E362924 entity
Predicate locatedNear P294 FINISHED
Object Rhein 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: Rhein | Statement: [Königsstuhl von Rhens, locatedNear, Rhein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rhein
Context triple: [Königsstuhl von Rhens, locatedNear, Rhein]
  • 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. 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.
  • C. Averser Rhein
    Averser Rhein is a mountain river in the Swiss canton of Graubünden that flows through the remote Avers valley and contributes to the headwaters of the Rhine system.
  • D. RHINE
    RHINE is a pivotal phase III clinical trial evaluating faricimab for the treatment of diabetic macular edema.
  • E. Rheine
    Rheine is a German city in the state of North Rhine-Westphalia, known for its historical town center and location along the River Ems.
  • 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_69d85a09a39c81908759f23268e2d408 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0067995fc8190b048f15086bd42f0 completed April 15, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_6a004f372f7c8190ba04b8bd13bff95c completed May 10, 2026, 9:26 a.m.
Created at: April 10, 2026, 3:09 a.m.