Triple
T2896208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodore of Mopsuestia |
E63945
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Antiochene theologian |
C11651
|
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: Antiochene theologian Context triple: [Theodore of Mopsuestia, instanceOf, Antiochene theologian]
-
A.
Syriac Christian theologian
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.
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.
-
C.
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.
-
D.
Patriarch of Alexandria
The Patriarch of Alexandria is the senior ecclesiastical leader and bishop who heads one of the historic Christian patriarchates based in Alexandria, traditionally overseeing the spiritual and administrative affairs of the church in Egypt and surrounding regions.
-
E.
Byzantine jurist
A Byzantine jurist is a legal scholar or judge of the Byzantine Empire who interpreted, applied, and commented on Roman and Byzantine law within the empire’s complex religious and imperial framework.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
Created at: March 6, 2026, 10:08 p.m.