Triple

T16028190
Position Surface form Disambiguated ID Type / Status
Subject Gemeente Arnhem E388771 entity
Predicate locatedOnRiver P165 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: [Gemeente Arnhem, locatedOnRiver, Rhine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rhine
Context triple: [Gemeente Arnhem, locatedOnRiver, 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. RHINE
    RHINE is a pivotal phase III clinical trial evaluating faricimab for the treatment of diabetic macular edema.
  • 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. 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.
  • E. the Rhoyne
    The Rhoyne is a vast and storied river in Essos, famed for its rich history, ruined Rhoynar cities, and strategic importance to traders and travelers in the world of *A Song of Ice and Fire*.
  • 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_69d86dada3808190825d5f80d72fbe88 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e183294984819080b8727a3511a21b completed April 17, 2026, 12:47 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0007757ed48190813f6ab839240a15 completed May 10, 2026, 4:20 a.m.
Created at: April 10, 2026, 4:56 a.m.