Triple
T28540066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plague Prayers of Mursili II |
E722266
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hittite prayer text |
C54227
|
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: Hittite prayer text Context triple: [Plague Prayers of Mursili II, instanceOf, Hittite prayer text]
-
A.
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.
-
B.
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.
-
C.
Assyrian royal inscription
An Assyrian royal inscription is a formal cuneiform text commissioned by an Assyrian king to record and glorify his military campaigns, building projects, piety, and divine legitimacy.
-
D.
Proto-Canaanite inscription
A Proto-Canaanite inscription is an early alphabetic text, typically carved on stone or pottery in the Levant during the late second millennium BCE, representing one of the earliest known stages of the Canaanite (and thus later Phoenician and Hebrew) writing system.
-
E.
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.
- F. None of above. chosen
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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:34 a.m.