Triple
T23384412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Þór |
E593836
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Þrúðvangr |
—
|
NE NERFINISHED |
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: Þrúðvangr | Statement: [Þór, residence, Þrúðvangr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Þrúðvangr Context triple: [Þór, residence, Þrúðvangr]
-
A.
Þrúðvangr
chosen
Þrúðvangr is the mythological realm in Norse cosmology that serves as the home and estate of the god Thor.
-
B.
Þrúðr
Þrúðr is a minor Norse goddess or valkyrie associated with strength, known as the daughter of Thor and the giantess Sif in Norse mythology.
-
C.
Vafþrúðnir
Vafþrúðnir is a wise and powerful giant in Norse mythology renowned for his knowledge, especially as depicted in his riddle contest with Odin.
-
D.
Erlingr
Erlingr is a variant form of the Scandinavian given name Erling, traditionally associated with Norse and Germanic origins.
-
E.
Hamðir
Hamðir is a legendary hero from Norse mythology, known primarily as one of the avenging sons of Guðrún in the Völsung cycle.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a497661c8190b52fa27419594989 |
completed | April 29, 2026, 6:26 a.m. |
Created at: April 17, 2026, 5:34 p.m.