Triple
T30106860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irkalla |
E765156
|
entity |
| Predicate | hasAfterlifeCondition |
P48829
|
FINISHED |
| Object | shadowy existence |
—
|
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: shadowy existence | Statement: [Irkalla, hasAfterlifeCondition, shadowy existence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAfterlifeCondition Context triple: [Irkalla, hasAfterlifeCondition, shadowy existence]
-
A.
hasAfterlifeElement
Indicates that something includes, depicts, or is associated with an element related to an afterlife or post-mortem existence.
-
B.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
C.
afterlife
Indicates a relationship where an entity exists or experiences a state following physical death or the end of mortal life.
-
D.
associatedAfterlife
chosen
Indicates a relationship where an entity is linked to, or characterized by, a particular concept, realm, or state of existence after death.
-
E.
afterDeathOf
Indicates that one event, state, or condition occurs subsequent to and as a result of the death of a specified 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67dbaf34c8190b9ce6f3d9cbad03d |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:09 p.m.