Triple

T8200693
Position Surface form Disambiguated ID Type / Status
Subject Linn E191563 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: [Linn, locatedNear, Rhein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rhein
Context triple: [Linn, 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. 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.
  • D. Rhein II
    Rhein II is a large-scale color photograph by German visual artist Andreas Gursky, renowned for its minimalist depiction of the Rhine River and for once being the most expensive photograph ever sold at auction.
  • E. Meuse
    The Meuse is a major European river flowing through France, Belgium, and the Netherlands, historically important for transport, trade, and the development of surrounding regions.
  • 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_69ca82c6e9548190a4c5ca14516e4417 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb5df6e7548190846a1afd62ec6d0a completed March 31, 2026, 5:39 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfab01c58c81909148dacad2dc7667 completed April 3, 2026, 11:56 a.m.
Created at: March 30, 2026, 5:43 p.m.