Triple
T20710068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | corpus of Maximus the Confessor |
E509010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theological corpus |
C25962
|
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: theological corpus Context triple: [corpus of Maximus the Confessor, instanceOf, theological corpus]
-
A.
Christian theological corpus
chosen
The Christian theological corpus is the body of writings, doctrines, and interpretive traditions that systematically articulate and reflect on Christian beliefs about God, Christ, salvation, the Church, and the ultimate destiny of creation.
-
B.
theological work
A theological work is a written or spoken scholarly exploration that systematically examines, interprets, and articulates beliefs about the nature of the divine, religious doctrines, and their implications for faith and practice.
-
C.
theological library
A theological library is a specialized collection of books, manuscripts, digital resources, and reference materials focused on religious studies, sacred texts, theology, and related disciplines, organized to support research, education, and spiritual inquiry.
-
D.
theological document
A theological document is a written work that systematically explores, explains, or argues about religious beliefs, doctrines, and practices within a particular faith tradition.
-
E.
theological journal
A theological journal is a periodical publication that presents scholarly research, critical essays, and reflections on religious beliefs, doctrines, practices, and their implications for faith and society.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:14 p.m.