Triple
T3660953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gungnir |
E77645
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Sleipnir |
E250351
|
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: Sleipnir | Statement: [Gungnir, relatedTo, Sleipnir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sleipnir Context triple: [Gungnir, relatedTo, Sleipnir]
-
A.
Sleipnir
chosen
Sleipnir is the eight-legged, supernaturally fast horse of Norse mythology, renowned as the steed of the god Odin.
-
B.
Éljúðnir
Éljúðnir is the grim, mist-filled hall in Norse mythology that serves as the abode of the dead ruled over by the goddess Hel.
-
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.
Muninn
Muninn is one of the two ravens in Norse mythology who serve Odin by flying across the world to gather and report information back to him.
-
E.
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.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d6fa188190a6db5bdae7083573 |
completed | March 8, 2026, 6:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4c39796648190a83a7f1a63c653bd |
completed | March 14, 2026, 2:10 a.m. |
Created at: March 8, 2026, 3:25 p.m.