Triple
T38549180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paulinus of Antioch |
E925058
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bishop of Antioch |
C13446
|
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: Bishop of Antioch Context triple: [Paulinus of Antioch, instanceOf, Bishop of Antioch]
-
A.
Archbishop of Antioch
The Archbishop of Antioch is a senior ecclesiastical leader who serves as the chief bishop and spiritual head of a major Christian see historically centered in the ancient city of Antioch.
-
B.
patriarch of Antioch
chosen
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.
-
C.
Bishop of Myra
The Bishop of Myra is a high-ranking Christian cleric responsible for overseeing the spiritual, administrative, and pastoral life of the diocese centered in the ancient city of Myra.
-
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.
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.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.