Triple
T15552668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aesir at Ragnarök |
E370790
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norse mythological concept |
C5546
|
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: Norse mythological concept Context triple: [Aesir at Ragnarök, instanceOf, Norse mythological concept]
-
A.
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.
-
B.
being in Norse mythology
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.
-
C.
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.
-
D.
mythological concept
chosen
A mythological concept is an abstract idea, force, or principle originating in mythic narratives that helps explain the nature of the world, human experience, or the divine within a particular cultural tradition.
-
E.
entity in Norse cosmology
An entity in Norse cosmology is any being, force, or realm—such as gods, giants, humans, spirits, or worlds—that participates in and shapes the mythic structure of the Norse universe.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:08 a.m.