Triple
T3551468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fenrir |
E75119
|
entity |
| Predicate | otherNames |
P39
|
FINISHED |
| Object | Fenris Wolf |
E75119
|
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: Fenris Wolf | Statement: [Fenrir, otherNames, Fenris Wolf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fenris Wolf Context triple: [Fenrir, otherNames, Fenris Wolf]
-
A.
Fenrir
chosen
Fenrir is a monstrous wolf in Norse mythology prophesied to kill the god Odin during Ragnarök.
-
B.
Sköll
Sköll is a wolf from Norse mythology who chases the sun across the sky and is fated to devour it at Ragnarök.
-
C.
Níðhöggr
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.
-
D.
Jormungandr
Jormungandr is the colossal World Serpent of Norse mythology, destined to encircle Midgard and battle Thor during Ragnarök.
-
E.
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.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfd52f44819088e07139fe987e2a |
completed | March 8, 2026, 6:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4cdd2715c81908250bb2925de8e1f |
completed | March 14, 2026, 2:54 a.m. |
Created at: March 8, 2026, 3:20 p.m.