Triple
T861752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spiritual Exercises |
E18613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian devotional work |
C1830
|
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 devotional work Context triple: [Spiritual Exercises, instanceOf, Christian devotional work]
-
A.
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.
-
B.
Christian devotional title
A Christian devotional title is a spiritually themed name or phrase that encapsulates the focus, tone, and theological emphasis of a work intended to guide believers in prayer, reflection, and daily faith practice.
-
C.
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.
-
D.
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.
-
E.
religious literature
chosen
Religious literature is a body of written works—such as scriptures, theological treatises, devotional texts, and spiritual narratives—created to express, interpret, and transmit the beliefs, practices, values, and experiences of a religious tradition.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.