Triple
T15280791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hrungnir |
E365263
|
entity |
| Predicate | opponent |
P437
|
FINISHED |
| Object | Þórr |
E374610
|
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: Þórr | Statement: [Hrungnir, opponent, Þórr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Þórr Context triple: [Hrungnir, opponent, Þórr]
-
A.
Þórr
chosen
Þórr is the Norse god of thunder, storms, and protection, famed for wielding the hammer Mjölnir and defending gods and humans from giants.
-
B.
Týr
Týr is a Norse god associated with law, justice, and heroic glory, best known for sacrificing his hand to bind the monstrous wolf Fenrir.
-
C.
Þrymr
Þrymr is a giant (jötunn) from Norse mythology best known for stealing Thor’s hammer Mjölnir and demanding the goddess Freyja as his bride in exchange.
-
D.
Odin
Odin is the chief god in Norse mythology, associated with wisdom, war, poetry, and magic, and revered as the ruler of Asgard and the Aesir gods.
-
E.
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.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e504d8c8190ad6c565a31d1a9bd |
completed | April 15, 2026, 10:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a009183a94081909c5892b1ccbc1d7a |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 3:15 a.m.