Triple
T9872551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Severus of Antioch |
E239992
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Oriental Orthodox saint |
C22564
|
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: Oriental Orthodox saint Context triple: [Saint Severus of Antioch, instanceOf, Oriental Orthodox saint]
-
A.
Orthodox saint
An Orthodox saint is a person recognized by the Eastern Orthodox Church as having lived a life of exceptional holiness and faithfulness to God, serving as an intercessor and example for believers.
-
B.
Georgian Orthodox saint
A Georgian Orthodox saint is a holy person recognized by the Georgian Orthodox Church for their exemplary faith, virtuous life, and often martyrdom, and is venerated as an intercessor and model of Christian living.
-
C.
Armenian saint
chosen
An Armenian saint is a holy figure recognized within the Armenian Apostolic or Armenian Catholic traditions for exemplary faith, virtue, and often martyrdom, and venerated as an intercessor and spiritual model for the faithful.
-
D.
Orthodox Christian cleric
An Orthodox Christian cleric is an ordained minister within the Eastern Orthodox Church who leads liturgical worship, administers sacraments, provides spiritual guidance, and upholds the doctrines and traditions of the Orthodox faith.
-
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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:37 p.m.