Triple
T2282845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odin |
E51318
|
entity |
| Predicate | weapon |
P6948
|
FINISHED |
| Object | Gungnir |
E77645
|
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: Gungnir | Statement: [Odin, weapon, Gungnir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gungnir Context triple: [Odin, weapon, Gungnir]
-
A.
Gungnir
chosen
Gungnir is the legendary spear of the god Odin in Norse mythology, renowned for its unerring accuracy and powerful enchantments.
-
B.
Mjolnir
Mjolnir is the legendary hammer of the thunder god Thor in Norse mythology, renowned for its immense power, protection of the gods, and role as a symbol of divine authority and destruction.
-
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.
Aasrud
Aasrud is a Norwegian surname most notably borne by politician Rigmor Aasrud.
-
E.
Glamdring
Glamdring is the legendary Elven sword from J.R.R. Tolkien’s Middle-earth legendarium, famed for its use by Gandalf and its ability to glow in the presence of orcs.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc21d6d748190980128c1bc5b9621 |
completed | March 7, 2026, 6:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae71e8f7488190ab0c0c93910984fa |
completed | March 9, 2026, 7:08 a.m. |
Created at: March 4, 2026, 7:48 p.m.