Triple

T21557130
Position Surface form Disambiguated ID Type / Status
Subject Roderick E531921 entity
Predicate etymologicalRoot P453 FINISHED
Object Hrōþirīks 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: Hrōþirīks | Statement: [Roderick, etymologicalRoot, Hrōþirīks]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hrōþirīks
Context triple: [Roderick, etymologicalRoot, Hrōþirīks]
  • A. Hrólfr
    Hrólfr, better known as Rollo, was a Viking leader who became the first ruler of Normandy in the early 10th century.
  • B. Hrœrekr chosen
    Hrœrekr is the Old Norse form of the name Rurik, the semi-legendary Varangian chieftain traditionally regarded as the founder of the Rurikid dynasty in early medieval Rus'.
  • C. Þrúðr
    Þrúðr is a minor Norse goddess or valkyrie associated with strength, known as the daughter of Thor and the giantess Sif in Norse mythology.
  • D. Hjálmar
    Hjálmar is a masculine given name of Old Norse origin, traditionally used in Scandinavian countries.
  • E. Högni
    Högni is a legendary Norse hero and warrior from the Völsung and Nibelung traditions, often depicted as a brave but tragic figure caught in cycles of betrayal and revenge.
  • 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_69e0c460232c81908de2c3819d17c00e completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eed2e04b048190ac3a9913094b4625 completed April 27, 2026, 3:07 a.m.
Created at: April 16, 2026, 6:29 p.m.