Triple
T3441916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aesir–Vanir War |
E72583
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Freyr |
E73326
|
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: Freyr | Statement: [Aesir–Vanir War, relatedTo, Freyr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Freyr Context triple: [Aesir–Vanir War, relatedTo, Freyr]
-
A.
Freyr
chosen
Freyr is a major Norse god associated with fertility, prosperity, sunshine, and fair weather, often revered as a bringer of peace and good harvests.
-
B.
Baldr
Baldr is a radiant and beloved Norse god associated with light, purity, and beauty, whose death is a central and tragic event in Norse mythology.
-
C.
Njord
Njord is a Norse god associated primarily with the sea, seafaring, wind, and wealth, especially revered by sailors and fishermen.
-
D.
Hermóðr
Hermóðr is a figure in Norse mythology, often depicted as a brave messenger of the gods who rides to Hel on Odin’s behalf.
-
E.
Ullr
Ullr is a Norse god associated with skiing, archery, and winter, often regarded as a skilled hunter and warrior.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba276b708190949f294a8d09ec7b |
completed | March 8, 2026, 6:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b367fa3bc48190a3ed0bb8a5d8e8b2 |
completed | March 13, 2026, 1:27 a.m. |
Created at: March 8, 2026, 3:16 p.m.