Triple
T33191841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chronicon Syriacum |
E849630
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Syriac literary work |
C26985
|
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: Syriac literary work Context triple: [Chronicon Syriacum, instanceOf, Syriac literary work]
-
A.
Syriac Christian literature
chosen
Syriac Christian literature encompasses the body of religious, theological, liturgical, and poetic writings composed in the Syriac language by Christian communities from late antiquity onward, reflecting their doctrinal debates, spiritual practices, and cultural interactions across the Middle East and beyond.
-
B.
Hebrew literary work
A Hebrew literary work is a written creation composed primarily in the Hebrew language, encompassing genres such as poetry, prose, drama, and religious or secular texts that reflect Hebrew culture, history, and thought.
-
C.
Manichaean religious text
A Manichaean religious text is a written work that conveys the dualistic doctrines, cosmology, ethics, and ritual practices of the Manichaean faith, often framed as revelations or teachings from Mani and other divine figures.
-
D.
Syriac Christian poet
A Syriac Christian poet is a writer who composes religious and often liturgical verse in the Syriac language, blending biblical themes, theology, and local cultural motifs within the Syriac Christian tradition.
-
E.
ancient literary work
An ancient literary work is a written composition created in antiquity that reflects the language, culture, beliefs, and artistic expression of early civilizations.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:29 a.m.