Triple
T28159462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Спасо-Преображенский монастырь |
E714849
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | монастырь Русской православной церкви |
C5781
|
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: монастырь Русской православной церкви Context triple: [Спасо-Преображенский монастырь, instanceOf, монастырь Русской православной церкви]
-
A.
Eastern Orthodox monastery
chosen
An Eastern Orthodox monastery is a religious community where monks or nuns live a communal life of prayer, worship, asceticism, and service according to the traditions and spiritual practices of the Eastern Orthodox Church.
-
B.
Byzantine-rite Catholic monastery
A Byzantine-rite Catholic monastery is a religious community of monks or nuns within the Catholic Church that follows the liturgical, spiritual, and canonical traditions of the Byzantine rite while remaining in full communion with the Pope.
-
C.
monastery church
A monastery church is a religious building within a monastic complex where monks or nuns gather for communal worship, prayer, and liturgical services.
-
D.
святой Русской православной церкви
Святой Русской православной церкви — это канонизированный церковью человек, признанный образцом христианской жизни и веры, к которому верующие обращаются с молитвами как к небесному заступнику.
-
E.
organ of the Russian Orthodox Church
An organ of the Russian Orthodox Church is a formal institutional body or administrative unit within the Church that carries out specific religious, governance, or organizational functions under its canonical authority.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:05 p.m.