Triple
T13487541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ugaritic Baal Cycle |
E318545
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ugaritic text |
C33097
|
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: Ugaritic text Context triple: [Ugaritic Baal Cycle, instanceOf, Ugaritic text]
-
A.
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.
-
B.
cuneiform script
Cuneiform script is one of the earliest known systems of writing, developed by the ancient Sumerians of Mesopotamia, characterized by wedge-shaped marks impressed on clay tablets.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:42 p.m.