Triple
T17515109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exposition of the Orthodox Faith |
E426548
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dogmatic theology text |
C5069
|
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: dogmatic theology text Context triple: [Exposition of the Orthodox Faith, instanceOf, dogmatic theology text]
-
A.
theological document
chosen
A theological document is a written work that systematically explores, explains, or argues about religious beliefs, doctrines, and practices within a particular faith tradition.
-
B.
Christian theological corpus
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.
-
C.
doctrinal system
A doctrinal system is an organized, coherent set of principles, beliefs, or teachings that provides a structured framework for understanding, interpreting, and guiding thought or behavior within a particular domain.
-
D.
Reformed theology text
A Reformed theology text is a written work that systematically presents and explains Christian doctrine from the perspective of the Reformed tradition, emphasizing God’s sovereignty, covenant theology, and the authority of Scripture.
-
E.
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.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:49 a.m.