Triple
T5326191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgy Gapon |
E123191
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian Orthodox priest |
C17922
|
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: Russian Orthodox priest Context triple: [Georgy Gapon, instanceOf, Russian Orthodox priest]
-
A.
Russian Orthodox bishop
A Russian Orthodox bishop is a high-ranking cleric in the Russian Orthodox Church responsible for overseeing dioceses, administering sacraments, guiding clergy and laity, and preserving the traditions and doctrines of Eastern Orthodoxy within his jurisdiction.
-
B.
Serbian Orthodox priest
A Serbian Orthodox priest is a Christian cleric ordained in the Serbian Orthodox Church who leads liturgical services, administers sacraments, offers spiritual guidance, and upholds the traditions and teachings of Eastern Orthodoxy within the Serbian cultural and religious context.
-
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.
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.
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.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:59 p.m.