Triple
T15003023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book V (Divine Institutes) |
E374138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | volume of a theological work |
C5743
|
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: volume of a theological work Context triple: [Book V (Divine Institutes), instanceOf, volume of a theological work]
-
A.
theological work
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Orthodox Christian treatise
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.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:54 a.m.