Triple
T30214922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nergal and Ereshkigal |
E768177
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Near Eastern literary text |
C54229
|
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: ancient Near Eastern literary text Context triple: [Nergal and Ereshkigal, instanceOf, ancient Near Eastern literary text]
-
A.
ancient Mesopotamian text
An ancient Mesopotamian text is a written document from early civilizations in the Tigris-Euphrates region, typically inscribed on clay tablets in cuneiform script, recording everything from myths and laws to economic transactions and scholarly knowledge.
-
B.
ancient Near Eastern religious text
chosen
An ancient Near Eastern religious text is a written work from early civilizations of the Near East that records myths, rituals, laws, prayers, or theological reflections expressing the beliefs and practices of their religious traditions.
-
C.
Sumerian literary text
A Sumerian literary text is a written composition in the Sumerian language, typically preserved on clay tablets, that conveys narratives, hymns, myths, wisdom, or other imaginative and artistic content rather than purely administrative or practical information.
-
D.
ancient literary work
An ancient literary work is a written composition created in antiquity that reflects the language, culture, beliefs, and artistic expression of early civilizations.
-
E.
Ugaritic text
An Ugaritic text is an ancient written document from the city of Ugarit, inscribed in the Ugaritic cuneiform script and typically recording literary, religious, administrative, or legal content in the Ugaritic language.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:33 p.m.