Triple
T11882939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spell 125 |
E282700
|
entity |
| Predicate | consequenceOfSuccess |
P812
|
FINISHED |
| Object | admission to the blessed afterlife |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: admission to the blessed afterlife | Statement: [Spell 125, consequenceOfSuccess, admission to the blessed afterlife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfSuccess Context triple: [Spell 125, consequenceOfSuccess, admission to the blessed afterlife]
-
A.
significantEventConsequence
Indicates that one event leads to an important or impactful consequence for another event, state, or entity.
-
B.
announcedConsequence
Indicates that one entity has publicly stated or declared a specific outcome or consequence that will result from an action, event, or condition.
-
C.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
D.
consequenceOfCertification
Indicates that something occurs as a result of, or is caused by, a particular certification.
-
E.
releasedAfterSuccessOf
Indicates that one entity was released following, and likely in response to, the successful performance or reception of another entity.
- F. None of above.
Provenance (3 batches)
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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a02ad4819090faef0e0be732ee |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.