Triple
T10165599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustine’s anti-Pelagian writings |
E235197
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theological work 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 work corpus Context triple: [Augustine’s anti-Pelagian writings, instanceOf, theological work corpus]
-
A.
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.
-
B.
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.
-
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.
philosophical corpus
A philosophical corpus is a structured collection of philosophical texts, arguments, and commentaries that together represent the intellectual output of one or more thinkers, traditions, or periods.
-
E.
theological consortium
A theological consortium is a collaborative association of religious scholars, institutions, and organizations dedicated to advancing the study, dialogue, and application of theological thought across traditions.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:10 p.m.