Triple
T29047440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Day of Judgment |
E735172
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious eschatological event |
C619
|
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 event Context triple: [Day of Judgment, instanceOf, religious eschatological event]
-
A.
Christian eschatological event
chosen
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.
-
B.
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.
-
C.
religious phenomenon
A religious phenomenon is any observable event, practice, experience, or pattern of belief that arises within or in relation to a religious tradition, worldview, or sense of the sacred.
-
D.
eschatological doctrine
An eschatological doctrine is a systematic set of beliefs or teachings concerning the ultimate destiny of individuals and the world, including concepts of death, judgment, and the final state of existence.
-
E.
eschatological figure
An eschatological figure is a personified agent—divine, human, or supernatural—who plays a decisive role in bringing about, interpreting, or embodying the final events of history or the ultimate destiny of the world.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:06 a.m.