Triple
T17967622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Disappointment |
E449254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious historical event |
C27133
|
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 historical event Context triple: [Great Disappointment, instanceOf, religious historical event]
-
A.
historic event
chosen
A historic event is a significant occurrence in the past that has had a lasting impact on societies, cultures, or the course of history.
-
B.
event in church history
An event in church history is a significant occurrence or development within the life of the Christian church that influences its doctrine, practice, structure, or relationship with society over time.
-
C.
historical religious institution
A historical religious institution is an organized body or establishment that has played a significant role in shaping and preserving religious beliefs, practices, and cultural traditions over an extended period in history.
-
D.
historical event collection
A historical event collection is an organized set of documented occurrences from the past, grouped and structured to support analysis, comparison, and retrieval based on time, place, theme, or significance.
-
E.
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.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:22 a.m.