Triple
T31492839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Last Battle |
E803453
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian allegorical work |
C21742
|
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 allegorical work Context triple: [The Last Battle, instanceOf, Christian allegorical work]
-
A.
allegorical work
chosen
An allegorical work is a narrative or artistic creation in which characters, events, and settings symbolically represent abstract ideas, moral qualities, or political and social concepts beyond their literal meaning.
-
B.
Jewish apocalyptic work
A Jewish apocalyptic work is a religious text, typically from the Second Temple period, that reveals divine mysteries about the end of days, cosmic conflict, and ultimate judgment through symbolic visions and angelic mediators.
-
C.
Christian esoteric work
A Christian esoteric work is a text or practice that explores hidden, mystical, or symbolic dimensions of Christian theology and spirituality, often intended for initiates or advanced seekers rather than general believers.
-
D.
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.
-
E.
allegorical treatise
An allegorical treatise is a didactic written work that conveys moral, philosophical, or spiritual ideas through an extended system of symbolic characters, events, and narratives.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:39 p.m.