Triple
T15017280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ras Shamra tablets |
E377988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Near Eastern texts |
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: ancient Near Eastern texts Context triple: [Ras Shamra tablets, instanceOf, ancient Near Eastern texts]
-
A.
Ugaritic text
chosen
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.
ancient literature
Ancient literature encompasses the written works, myths, epics, religious texts, and philosophical writings produced by early civilizations that reveal their cultures, beliefs, and historical experiences.
-
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.
ancient Near Eastern law collection
An ancient Near Eastern law collection is a compiled set of legal rules, case decisions, and royal decrees from early civilizations such as Mesopotamia, intended to articulate social norms, regulate behavior, and legitimize authority.
-
E.
ancient Near Eastern religion
Ancient Near Eastern religion encompasses the diverse, interconnected religious beliefs, rituals, and mythologies of civilizations such as Sumer, Akkad, Babylonia, Assyria, Canaan, and Israel from the Bronze and Iron Ages.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:55 a.m.