Triple
T15428083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Móðguðr |
E369564
|
entity |
| Predicate | encounters |
P13259
|
FINISHED |
| Object | Hermóðr |
E261006
|
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: Hermóðr | Statement: [Móðguðr, encounters, Hermóðr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hermóðr Context triple: [Móðguðr, encounters, Hermóðr]
-
A.
Hermóðr
chosen
Hermóðr is a figure in Norse mythology, often depicted as a brave messenger of the gods who rides to Hel on Odin’s behalf.
-
B.
Höðr
Höðr is a blind god in Norse mythology best known for being tricked into killing his brother Baldr, an act that sets in motion events leading to Ragnarök.
-
C.
Vafþrúðnir
Vafþrúðnir is a wise and powerful giant in Norse mythology renowned for his knowledge, especially as depicted in his riddle contest with Odin.
-
D.
Hamðir
Hamðir is a legendary hero from Norse mythology, known primarily as one of the avenging sons of Guðrún in the Völsung cycle.
-
E.
Víðarr
Víðarr is a silent Norse god associated with vengeance and strength, prophesied to avenge Odin by slaying the wolf Fenrir at Ragnarök.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec31f4881908b26ff7c381d7bc9 |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0139e10e94819092b71606dbe4f5d5 |
completed | May 11, 2026, 2:07 a.m. |
Created at: April 10, 2026, 3:20 a.m.