Triple
T28173764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volodymyr Chekhivsky |
E715532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Orthodox church figure |
C54495
|
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: Orthodox church figure Context triple: [Volodymyr Chekhivsky, instanceOf, Orthodox church figure]
-
A.
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.
-
B.
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.
-
C.
representation of the Russian Orthodox Church
A representation of the Russian Orthodox Church models the institution’s hierarchical structure, doctrines, liturgical practices, cultural influences, and historical evolution within religious and social contexts.
-
D.
Russian Orthodox priest
A Russian Orthodox priest is a Christian cleric ordained in the Russian Orthodox Church who leads liturgical services, administers sacraments, offers spiritual guidance, and upholds the traditions and doctrines of Eastern Orthodoxy within his parish community.
-
E.
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.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:14 p.m.