Triple
T30163616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gudea inscriptions |
E766734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sumerian text corpus |
C47265
|
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 text corpus Context triple: [Gudea inscriptions, instanceOf, Sumerian text corpus]
-
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.
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.
-
C.
cuneiform document
chosen
A cuneiform document is a written artifact, typically on clay or stone, bearing information recorded in the wedge-shaped cuneiform script used by ancient Near Eastern civilizations.
-
D.
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.
-
E.
Old Babylonian period text
An Old Babylonian period text is a written document produced in Mesopotamia roughly between 2000–1600 BCE, typically inscribed in cuneiform on clay tablets and reflecting the administrative, legal, literary, or scholarly practices of that era.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:22 p.m.