Triple
T17515160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fount of Knowledge |
E426549
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian theological compendium |
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: Christian theological compendium Context triple: [Fount of Knowledge, instanceOf, Christian theological compendium]
-
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.
Christian theological category
A Christian theological category is a conceptual grouping used to organize and interpret doctrines, beliefs, and practices within the Christian faith according to shared themes or characteristics.
-
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 prayer book
A Christian prayer book is a collection of written prayers, liturgies, and devotional texts organized to guide individuals or congregations in worship and personal devotion according to Christian tradition.
-
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.
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.