Triple

T358513
Position Surface form Disambiguated ID Type / Status
Subject Limes Germanicus E7597 entity
Predicate follows P134 FINISHED
Object River 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: River Rhine | Statement: [Limes Germanicus, follows, River Rhine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Rhine
Context triple: [Limes Germanicus, follows, River 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. 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.
  • C. Weser
    The Weser is a major river in northwestern Germany that flows through several federal states before emptying into the North Sea.
  • D. Elbe
    The Elbe is one of Central Europe's major rivers, flowing from the Czech Republic through Germany to the North Sea and serving as an important waterway for transport, industry, and agriculture.
  • E. Ems
    The Ems is a river in northwestern Germany that flows through several states before emptying into the North Sea.
  • 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_69a2e7e696948190bebc966535995e45 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ebb0e348819086e3ccd96c7b129e completed Feb. 28, 2026, 1:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3e86386e08190a21d34fea9faaef0 completed March 1, 2026, 7:18 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.