Triple

T17388620
Position Surface form Disambiguated ID Type / Status
Subject Hruodperht E422755 entity
Predicate alternativeTransliteration P5923 FINISHED
Object Hrodperht NE NERFINISHED

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: Hrodperht | Statement: [Hruodperht, alternativeTransliteration, Hrodperht]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hrodperht
Context triple: [Hruodperht, alternativeTransliteration, Hrodperht]
  • A. Hruodperht chosen
    Hruodperht is an early Germanic personal name of Old High German origin that later evolved into the modern given name Rupert.
  • B. Níðhǫggr
    Níðhǫggr is a dragon or serpent in Norse mythology that gnaws at the roots of the world tree Yggdrasil and is associated with destruction and the punishment of the wicked.
  • C. Hoddmímir
    Hoddmímir is a figure in Norse mythology, often associated with a wise being or forest linked to the survival of humans after Ragnarök.
  • D. Eyvind
    Eyvind is a masculine given name of Old Norse origin, historically associated with Scandinavian culture and borne by figures such as the American artist Eyvind Earle.
  • E. Ingemund
    Ingemund is a Scandinavian masculine given name of Old Norse origin, historically borne by several notable figures in Sweden and Norway.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889d710288190bf0f4762801fefae completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a8b66288190b29bb82eff761902 completed April 19, 2026, 2:14 a.m.
Created at: April 10, 2026, 5:45 a.m.