Triple
T5337940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isaac of Nineveh |
E123871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Syriac Christian bishop |
C8651
|
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 Christian bishop Context triple: [Isaac of Nineveh, instanceOf, Syriac Christian bishop]
-
A.
Syriac Christian bishop
chosen
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.
-
B.
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.
-
C.
Eastern Orthodox bishop
An Eastern Orthodox bishop is a high-ranking cleric who holds apostolic succession and oversees the spiritual, liturgical, and administrative life of a diocese within the Eastern Orthodox Church.
-
D.
patriarch of Antioch
The patriarch of Antioch is the senior ecclesiastical leader and chief bishop of one of the ancient Christian sees centered in Antioch, historically overseeing doctrine, liturgy, and church governance for his jurisdiction.
-
E.
4th-century Christian bishop
A 4th-century Christian bishop was a high-ranking church leader responsible for overseeing a Christian community, defending orthodoxy amid theological controversies, and guiding the church through the transition from persecution to imperial favor.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2 p.m.