Triple

T706412
Position Surface form Disambiguated ID Type / Status
Subject Leiden E14108 entity
Predicate locatedOn P40 FINISHED
Object New Rhine E103757 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: New Rhine | Statement: [Leiden, locatedOn, New Rhine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: New Rhine
Context triple: [Leiden, locatedOn, New Rhine]
  • A. 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.
  • B. Old Rhine chosen
    The Old Rhine is a historic branch of the Rhine River in the western Netherlands that flows through cities such as Leiden before reaching the North Sea.
  • C. Rhine
    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.
  • D. Leine
    The Leine is a major river in central Germany that flows through the federal state of Lower Saxony, passing cities such as Göttingen and Hanover before joining the Aller.
  • 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_69a493494ec48190ae6751683625a9ba completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a54607f08190b3ee4805f2ea4b2f completed March 1, 2026, 8:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69a7c005750881909187edfa8e8fa02c completed March 4, 2026, 5:15 a.m.
Created at: March 1, 2026, 7:36 p.m.