Triple
T21583162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great Asceticon |
E532570
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Orthodox monastic text |
C16844
|
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: Eastern Orthodox monastic text Context triple: [The Great Asceticon, instanceOf, Eastern Orthodox monastic text]
-
A.
Orthodox Christian treatise
chosen
An Orthodox Christian treatise is a formal written work that systematically explains, defends, or reflects upon the doctrines, spiritual life, and liturgical practices of the Eastern Orthodox Church in light of Scripture and Holy Tradition.
-
B.
Eastern Orthodox monk
An Eastern Orthodox monk is a man who has taken religious vows within the Eastern Orthodox Church, dedicating his life to prayer, asceticism, communal or solitary monastic living, and the pursuit of spiritual union with God.
-
C.
Eastern Orthodox monastery
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.
-
D.
Eastern Orthodox reference work
A comprehensive resource that systematically presents, explains, and documents the beliefs, practices, history, and canonical texts of the Eastern Orthodox Church.
-
E.
early medieval religious text
An early medieval religious text is a written work produced roughly between the 5th and 11th centuries that conveys, interprets, or codifies spiritual beliefs, practices, or doctrines within a particular religious tradition.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:31 p.m.