Triple
T31256504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lugalbanda |
E796988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sumerian mythological figure |
C17299
|
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 mythological figure Context triple: [Lugalbanda, instanceOf, Sumerian mythological figure]
-
A.
Mesopotamian legendary figure
chosen
A Mesopotamian legendary figure is a mythic or semi-divine personage from ancient Mesopotamian cultures whose stories, deeds, and attributes embody religious beliefs, moral values, and cosmological ideas preserved in epics, hymns, and ritual texts.
-
B.
Mesopotamian deity
A Mesopotamian deity is a divine being from the ancient cultures of Sumer, Akkad, Assyria, and Babylonia, associated with specific cosmic, natural, or societal domains and worshiped through rituals, temples, and myths.
-
C.
Babylonian god
A Babylonian god is a divine being from ancient Mesopotamian religion, associated with specific cosmic functions, cities, or aspects of life, and worshiped through rituals, temples, and myths.
-
D.
Sumerian person
A Sumerian person is an individual belonging to the ancient Sumerian civilization of southern Mesopotamia, characterized by their participation in early urban society, cuneiform literacy, polytheistic religion, and agrarian-based economy.
-
E.
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.
- 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:12 p.m.