Triple
T34162018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lóðurr (in some scholarly theories) |
E876302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hypothesized figure in Norse mythology |
C34821
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: hypothesized figure in Norse mythology Context triple: [Lóðurr (in some scholarly theories), instanceOf, hypothesized figure in Norse mythology]
-
A.
being in Norse mythology
chosen
A being in Norse mythology is any supernatural or mythic entity—such as a god, giant, dwarf, or spirit—that inhabits and shapes the cosmological and narrative world of Norse myth.
-
B.
structure in Norse mythology
A structure in Norse mythology is any significant built or naturally formed place—such as halls, fortresses, bridges, or cosmic frameworks—that serves as a setting for divine, heroic, or cosmological events within the Norse mythic cosmos.
-
C.
figure in Finnish mythology
A figure in Finnish mythology is a supernatural or legendary being, deity, hero, or spirit that appears in Finland’s traditional stories, beliefs, and epic poetry such as the Kalevala.
-
D.
artifact in Norse mythology
An artifact in Norse mythology is a legendary object—often imbued with magical properties or divine origin—that plays a significant role in the myths, powers, and fates of gods, heroes, and cosmic events.
-
E.
place in Norse mythology
A place in Norse mythology is a mythic location—such as a realm, world, or specific site—imbued with cultural, spiritual, or cosmological significance within the Norse mythological cosmos.
- F. None of above.
Provenance (1 batch)
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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:54 a.m.