Triple
T35308502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahl al-Jannah |
E1019702
|
entity |
| Predicate | hasAfterlifeStatus |
P48829
|
FINISHED |
| Object | saved |
—
|
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: saved | Statement: [Ahl al-Jannah, hasAfterlifeStatus, saved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAfterlifeStatus Context triple: [Ahl al-Jannah, hasAfterlifeStatus, saved]
-
A.
hasAfterlifeElement
Indicates that something includes, depicts, or is associated with an element related to an afterlife or post-mortem existence.
-
B.
revivedAfter
Indicates that one entity comes back to life or is restored to a living or active state after a period of being dead, inactive, or nonfunctional, following another event or time point.
-
C.
diedAfter
Indicates that one entity’s death occurred later in time than another entity’s death.
-
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.
hasLifetimeStatus
Indicates that an entity is associated with a status or condition that applies for the entire duration of its existence.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.