Triple
T2196207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De veritate religionis Christianae |
E49979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian apologetics text |
C1921
|
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 apologetics text Context triple: [De veritate religionis Christianae, instanceOf, Christian apologetics text]
-
A.
Christian apologetic work
chosen
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.
-
B.
Christian sacred text
A Christian sacred text is a written work regarded by Christians as divinely inspired or authoritative for faith, doctrine, and practice, such as the Bible and related canonical or devotional writings.
-
C.
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.
-
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 belief
Christian belief is a faith-centered worldview grounded in the life, teachings, death, and resurrection of Jesus Christ, affirming salvation through Him and guiding moral, spiritual, and communal practices based on the Bible.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:46 p.m.