Triple

T6385114
Position Surface form Disambiguated ID Type / Status
Subject Ragnar E143680 entity
Predicate hasVariant P455 FINISHED
Object Ragnarr E143680 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: Ragnarr | Statement: [Ragnar, hasVariant, Ragnarr]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ragnarr
Context triple: [Ragnar, hasVariant, Ragnarr]
  • A. Ragnar chosen
    Ragnar is a masculine given name of Old Norse origin, historically associated with Viking-age Scandinavia and later borne by various notable figures.
  • B. Þ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.
  • C. Halfdan Ragnarsson
    Halfdan Ragnarsson was a 9th-century Viking warlord, traditionally identified as one of the sons of Ragnar Lothbrok, who played a major role in the Norse invasions and political upheavals in England.
  • D. Hrœrekr
    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'.
  • E. Raginmund
    Raginmund is a Germanic personal name of early medieval origin that later evolved into forms such as the Spanish given name Ramón.
  • 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_69c008dac1ec81909cef8157ccd69962 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0686764648190864163d390db292d completed March 22, 2026, 10:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69c638791ce8819081aeec3b11e1c96e completed March 27, 2026, 7:57 a.m.
Created at: March 22, 2026, 4:34 p.m.