Triple
T26062225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Day of Reckoning |
E657290
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious eschatological concept |
C31309
|
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: religious eschatological concept Context triple: [Day of Reckoning, instanceOf, religious eschatological concept]
-
A.
theological concept
A theological concept is an abstract idea or principle used to understand, explain, or systematize beliefs about the nature of the divine, spiritual realities, and their relationship to the world and humanity.
-
B.
Religious concept
chosen
A religious concept is an abstract idea, belief, or principle related to the nature of the divine, spiritual reality, moral order, or sacred practices within a religious tradition.
-
C.
Christian eschatological event
A Christian eschatological event is a future, divinely ordained occurrence described in Christian theology that marks a key stage in God’s ultimate plan for judgment, redemption, and the consummation of history.
-
D.
Islamic eschatological event
An Islamic eschatological event is a divinely ordained occurrence described in Islamic theology and scripture that unfolds in the end times, signaling stages of the Last Day, resurrection, judgment, and the ultimate fate of creation.
-
E.
Zoroastrian eschatological concept
A Zoroastrian eschatological concept is a religious idea within Zoroastrianism that concerns the ultimate fate of the world and souls, including final judgment, cosmic renewal, and the triumph of good over evil.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:19 p.m.