Triple
T10185639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lausiac History |
E236901
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian hagiographical work |
C10140
|
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 hagiographical work Context triple: [Lausiac History, instanceOf, Christian hagiographical work]
-
A.
hagiographical collection
chosen
A hagiographical collection is an assemblage of texts or narratives that recount and celebrate the lives, virtues, and miracles of saints or holy figures, often for devotional or didactic purposes.
-
B.
Orthodox Christian treatise
An Orthodox Christian treatise is a formal written work that systematically explains, defends, or reflects upon the doctrines, spiritual life, and liturgical practices of the Eastern Orthodox Church in light of Scripture and Holy Tradition.
-
C.
Orthodox Christian hymnographic work
An Orthodox Christian hymnographic work is a liturgical or devotional text set to chant or song that poetically expresses and interprets the theology, feasts, saints, and spiritual life of the Orthodox Church.
-
D.
Christian polemical work
A Christian polemical work is a text written from a Christian perspective that argues against, critiques, or refutes opposing religious, philosophical, or ideological positions to defend or promote Christian doctrine.
-
E.
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.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:12 p.m.