Triple
T31037210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pishoy of Scetis |
E790881
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Egyptian Christian saint |
C26911
|
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: Egyptian Christian saint Context triple: [Pishoy of Scetis, instanceOf, Egyptian Christian saint]
-
A.
legendary Christian saint
A legendary Christian saint is a revered figure, often of uncertain historicity, whose life story blends pious tradition, miracle tales, and moral exemplarity to inspire faith and devotion within Christian communities.
-
B.
saint of the Oriental Orthodox Churches
chosen
A saint of the Oriental Orthodox Churches is a holy person recognized within the Oriental Orthodox tradition for exemplary faith, virtue, and often miracles, and venerated as an intercessor and model of Christian life.
-
C.
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.
-
D.
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.
-
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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:59 p.m.