Triple
T31113308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ugaritic texts |
E793013
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northwest Semitic literature |
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: Northwest Semitic literature Context triple: [Ugaritic texts, instanceOf, Northwest Semitic literature]
-
A.
Semitic culture
Semitic culture encompasses the shared linguistic, religious, and social traditions of peoples historically speaking Semitic languages, such as Arabs, Jews, and Assyrians, across the Middle East and surrounding regions.
-
B.
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.
-
C.
Semitic script
A Semitic script is a writing system historically used for Semitic languages, typically characterized by consonant-based alphabets (abjads) written from right to left.
-
D.
ancient Near Eastern religious text
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.
-
E.
Solomonic literature
Solomonic literature refers to a body of biblical and post-biblical writings attributed to King Solomon, characterized by wisdom teachings, proverbs, philosophical reflections, and sometimes mystical or magical themes.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:04 p.m.