Triple
T31840337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | expedition against Aratta |
E812785
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sumerian epic |
C25568
|
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: Sumerian epic Context triple: [expedition against Aratta, instanceOf, Sumerian epic]
-
A.
Mesopotamian creation epic
A Mesopotamian creation epic is a mythological narrative poem that explains the origins of the cosmos, gods, and human society in ancient Mesopotamia, often emphasizing divine conflict and the establishment of cosmic order.
-
B.
Sumerian mythological poem
chosen
A Sumerian mythological poem is an ancient Mesopotamian narrative verse that recounts the deeds of gods, heroes, and cosmic events, often explaining the origins of the world, social institutions, and divine-human relationships.
-
C.
Sumerian temple hymn
A Sumerian temple hymn is an ancient Mesopotamian poetic composition that praises a specific temple and its deity, celebrating the sacred space’s divine presence, power, and ritual significance.
-
D.
episode in the Epic of Gilgamesh
An episode in the Epic of Gilgamesh is a distinct narrative unit within the larger poem that presents a specific adventure, challenge, or transformation in Gilgamesh’s journey, contributing to the overarching themes of mortality, friendship, and the search for meaning.
-
E.
Sumerian lament
A Sumerian lament is an ancient Mesopotamian poetic composition, often voiced by a grieving deity or priest, that ritually mourns the destruction of a city, temple, or people and seeks reconciliation with the gods.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:49 p.m.