Triple

T15127066
Position Surface form Disambiguated ID Type / Status
Subject Atlakviða E361317 entity
Predicate featuresCharacter P626 FINISHED
Object Högni E1125070 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: Högni | Statement: [Atlakviða, featuresCharacter, Högni]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Högni
Context triple: [Atlakviða, featuresCharacter, Högni]
  • A. Högni chosen
    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.
  • B. Helgi
    Helgi is an Icelandic given name commonly used for males and rooted in Old Norse tradition.
  • C. Hjálmar
    Hjálmar is a masculine given name of Old Norse origin, traditionally used in Scandinavian countries.
  • D. Þ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.
  • E. 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'.
  • 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_69d85a06450081909c5a14ea9851a15e completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e005a1b9288190954f2d92549805e5 completed April 15, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69febfe6c9cc8190b15e81092faa8ccf completed May 9, 2026, 5:02 a.m.
Created at: April 10, 2026, 3:06 a.m.