Triple
T19464234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hodr |
E486951
|
entity |
| Predicate | hasBrother |
P363
|
FINISHED |
| Object | Hermod |
—
|
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: Hermod | Statement: [Hodr, hasBrother, Hermod]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hermod Context triple: [Hodr, hasBrother, Hermod]
-
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œnir
Hœnir is a somewhat enigmatic Norse god associated with the Aesir, known from mythic accounts as a companion of Odin and a survivor of Ragnarök in some traditions.
-
C.
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.
-
D.
Týr
Týr is a Norse god associated with law, justice, and heroic glory, best known for sacrificing his hand to bind the monstrous wolf Fenrir.
-
E.
Heimdal
Heimdal is a district in the city of Trondheim, Norway, known as a residential and commercial area serving as a local hub in the southern part of the municipality.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633cf95988190b13b2153e67d0cac |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 10, 2026, 1:39 p.m.