Triple
T32636624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leviathan |
E834360
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | figure in ancient Near Eastern mythology |
C3096
|
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: figure in ancient Near Eastern mythology Context triple: [Leviathan, instanceOf, figure in ancient Near Eastern mythology]
-
A.
figure in Greek mythology
A figure in Greek mythology is a character—divine, heroic, or monstrous—who appears in the traditional myths of ancient Greece and embodies cultural values, natural forces, or moral lessons.
-
B.
episode in Sumerian mythology
An episode in Sumerian mythology is a distinct narrative unit within Sumerian mythic tradition, depicting specific events, interactions among gods, humans, and supernatural beings, and conveying religious, moral, or cosmological themes.
-
C.
structure in Greek mythology
A structure in Greek mythology is any significant built or natural edifice—such as temples, palaces, labyrinths, or fortifications—imbued with divine influence, heroic deeds, or symbolic meaning within mythic narratives.
-
D.
Mesopotamian mythological place
A Mesopotamian mythological place is a legendary or sacred location from ancient Mesopotamian belief systems, such as heavens, underworlds, or divine cities, that features in myths, religious texts, and ritual narratives.
-
E.
mythological figure
chosen
A mythological figure is a legendary being or character from traditional stories and belief systems, often embodying cultural values, natural forces, or supernatural powers.
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:07 a.m.