Triple
T10913332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höðr |
E257754
|
entity |
| Predicate | nameVariant |
P744
|
FINISHED |
| Object | Hodr |
E486951
|
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: Hodr | Statement: [Höðr, nameVariant, Hodr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hodr Context triple: [Höðr, nameVariant, Hodr]
-
A.
Hodr
chosen
Hodr is a blind god in Norse mythology, best known for being tricked into killing his brother Baldr.
-
B.
Hoderi
Hoderi is a deity in Japanese mythology, known as the elder son of Ninigi-no-Mikoto and an ancestor of seafaring clans.
-
C.
Njord
Njord is a Norse god associated primarily with the sea, seafaring, wind, and wealth, especially revered by sailors and fishermen.
-
D.
Surtr
Surtr is a fire giant and ruler of Muspelheim in Norse mythology, prophesied to lead the forces of fire at Ragnarök and bring about the world's destruction.
-
E.
Hymir
Hymir is a giant from Norse mythology best known for his role in the myth of Thor’s fishing trip to catch the Midgard Serpent.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7707310b0819092d0140acc3c64ba |
completed | April 9, 2026, 9:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3a92e09648190ab39053521211743 |
completed | April 18, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:22 p.m.