Triple
T15100591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hvergelmir |
E360652
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Níðhöggr |
E360407
|
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: Níðhöggr | Statement: [Hvergelmir, associatedWith, Níðhöggr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Níðhöggr Context triple: [Hvergelmir, associatedWith, Níðhöggr]
-
A.
Níðhöggr
chosen
Níðhöggr is a fearsome dragon or serpent from Norse mythology that gnaws at the roots of the world tree Yggdrasil and is associated with chaos and destruction.
-
B.
Svaðilfari
Svaðilfari is a powerful stallion from Norse mythology, best known as the sire of Odin’s eight-legged horse Sleipnir and as the supernatural steed that helped a giant build the walls of Asgard.
-
C.
Jormungandr
Jormungandr is the colossal World Serpent of Norse mythology, destined to encircle Midgard and battle Thor during Ragnarök.
-
D.
Hrungnir
Hrungnir is a stone-skinned giant from Norse mythology famed for his duel with the god Thor.
-
E.
Jörmunrekkr
Jörmunrekkr is a legendary Gothic king in Norse mythology, best known for his cruel role in the tragic saga of Svanhildr and her avenging brothers.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00550007481909e02ee1d597a4d37 |
completed | April 15, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69febfdffb6081909012cf0707f5c9f5 |
completed | May 9, 2026, 5:02 a.m. |
Created at: April 10, 2026, 3:04 a.m.