Triple

T1862332
Position Surface form Disambiguated ID Type / Status
Subject Hyperion E34842 entity
Predicate hasMainLocation P40 FINISHED
Object Rhine River 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 River | Statement: [Hyperion, hasMainLocation, Rhine River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rhine River
Context triple: [Hyperion, hasMainLocation, Rhine River]
  • 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. 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.
  • C. 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.
  • D. Old Rhine
    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.
  • E. Rhine–Meuse river system
    The Rhine–Meuse river system is a major interconnected river network in Western Europe that drains large parts of the Alps and low countries before emptying into the North Sea through multiple distributaries.
  • 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_69a88600b2f88190bc09303e68ab517e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abb09e714881909cef0f7e77b5b3b9 completed March 7, 2026, 4:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69afbba693f08190aead3b593f081c62 completed March 10, 2026, 6:35 a.m.
Created at: March 4, 2026, 7:34 p.m.