Triple
T4760180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apocryphal New Testament writings |
E105680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian apocrypha |
C12106
|
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 apocrypha Context triple: [Apocryphal New Testament writings, instanceOf, Christian apocrypha]
-
A.
Old Testament apocrypha
Old Testament apocrypha are a collection of ancient Jewish writings, not included in the Hebrew Bible, that expand upon or supplement Old Testament narratives and teachings and are considered canonical by some Christian traditions but not by others.
-
B.
apocryphal gospel
An apocryphal gospel is a non-canonical early Christian text, often narrating the life or teachings of Jesus, that was excluded from the official New Testament and typically regarded as of doubtful or disputed authenticity.
-
C.
apocryphal book
chosen
An apocryphal book is a work of uncertain or disputed authorship or canonical status, often associated with religious traditions but not officially accepted into the standard scriptural canon.
-
D.
Christian apologetic work
A Christian apologetic work is a text or presentation that systematically defends and explains the truth claims of Christianity using theological, philosophical, historical, and sometimes scientific arguments.
-
E.
Christian text tradition
The Christian text tradition is the historical process by which Christian writings—especially the Bible and related theological, liturgical, and devotional texts—are composed, transmitted, translated, interpreted, and canonized within Christian communities over time.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:20 p.m.