Triple
T15585563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Þórr |
E374610
|
entity |
| Predicate | goat |
P119312
|
FINISHED |
| Object | Tanngrisnir |
E292272
|
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: Tanngrisnir | Statement: [Þórr, goat, Tanngrisnir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tanngrisnir Context triple: [Þórr, goat, Tanngrisnir]
-
A.
Tanngrisnir
chosen
Tanngrisnir is one of the two magical goats in Norse mythology that serve as Thor’s steeds, pulling his thunderous chariot and being able to be eaten and resurrected.
-
B.
Bilskirnir
Bilskirnir is the immense, many-roomed hall of the thunder god Thor in Norse mythology, located in the region of Þrúðvangar.
-
C.
Draupnir
Draupnir is a magical gold ring in Norse mythology, forged by dwarves, that multiplies itself by producing eight new rings every ninth night.
-
D.
Hrungnir
Hrungnir is a stone-skinned giant from Norse mythology famed for his duel with the god Thor.
-
E.
Fáfnir
Fáfnir is a fearsome dragon from Norse mythology, originally a dwarf transformed by greed, who is slain by the hero Sigurd.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e4900408190aadb48b001db4169 |
completed | April 16, 2026, 2:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4c5166d88190ab14c7779e3e8e1f |
completed | May 9, 2026, 3:01 p.m. |
Created at: April 10, 2026, 4:11 a.m.