Triple

T3002738
Position Surface form Disambiguated ID Type / Status
Subject Rijn E81826 entity
Predicate tributary P415 FINISHED
Object Sieg E77328 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: Sieg | Statement: [Rijn, tributary, Sieg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sieg
Context triple: [Rijn, tributary, Sieg]
  • A. Sieg chosen
    The Sieg is a river in western Germany that flows through North Rhine-Westphalia and Rhineland-Palatinate before joining the Rhine.
  • B. Reinhard
    Reinhard is a masculine German given name historically borne by several notable figures, including high-ranking officials in Nazi Germany.
  • C. Heinrici
    Heinrici is a German surname most notably associated with Gotthard Heinrici, a senior Wehrmacht general during World War II.
  • D. Helmuth
    Helmuth is a masculine given name of German origin, historically borne by several notable military and political figures.
  • E. Otto the Illustrious
    Otto the Illustrious was a powerful 9th–10th century German nobleman of the Liudolfing dynasty whose rule and lineage laid the groundwork for the rise of the Ottonian Holy Roman Emperors.
  • 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_69ad8b1c4de88190a83b7cefaa1f2842 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9a1371c481909e214234afed1a65 completed March 8, 2026, 3:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b12e4f02248190890eb3944299bd15 completed March 11, 2026, 8:56 a.m.
Created at: March 8, 2026, 2:59 p.m.