Triple
T17923803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book I (Ad Uxorem) |
E448139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian treatise section |
C40073
|
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: Christian treatise section Context triple: [Book I (Ad Uxorem), instanceOf, Christian treatise section]
-
A.
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.
-
B.
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.
-
C.
Christian instructional manual
A Christian instructional manual is a structured guide that explains Christian beliefs, practices, and moral teachings, providing step-by-step direction for living according to biblical principles.
-
D.
Christian polemical work
A Christian polemical work is a text written from a Christian perspective that argues against, critiques, or refutes opposing religious, philosophical, or ideological positions to defend or promote Christian doctrine.
-
E.
Christian doctrine
Christian doctrine is the organized body of beliefs and teachings derived from the Bible and Christian tradition that defines the faith’s understanding of God, salvation, morality, and the church.
- F. None of above. chosen
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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:20 a.m.