Triple
T32034430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignatius Zakka I Iwas |
E818053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Syriac scholar |
C8652
|
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 scholar Context triple: [Ignatius Zakka I Iwas, instanceOf, Syriac scholar]
-
A.
Syriac Christian theologian
chosen
A Syriac Christian theologian is a scholar or religious thinker who develops, interprets, and systematizes Christian doctrine within the Syriac linguistic, liturgical, and cultural tradition.
-
B.
Byzantine scholar
A Byzantine scholar is a learned individual specializing in the language, theology, history, and culture of the Byzantine Empire, often engaging in the preservation, interpretation, and commentary of classical and Christian texts.
-
C.
Babylonian scholar
A Babylonian scholar is an educated individual in ancient Mesopotamia who studies, preserves, and interprets knowledge in fields such as astronomy, mathematics, divination, and literature, often serving in temples or royal courts.
-
D.
Syriac Christian bishop
A Syriac Christian bishop is a high-ranking cleric within the Syriac Christian traditions who oversees dioceses, administers sacraments, preserves Syriac liturgical and theological heritage, and provides spiritual and administrative leadership to clergy and laity.
-
E.
Syriac Christian monk
A Syriac Christian monk is a member of an ascetic religious community within the Syriac Christian tradition, devoted to prayer, contemplation, and communal or solitary monastic life shaped by Syriac liturgy, language, and theology.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:18 a.m.