Triple
T14655274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naraka |
E344091
|
entity |
| Predicate | fateAfterExit |
P23287
|
FINISHED |
| Object | rebirth in another realm |
—
|
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: rebirth in another realm | Statement: [Naraka, fateAfterExit, rebirth in another realm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateAfterExit Context triple: [Naraka, fateAfterExit, rebirth in another realm]
-
A.
afterlifeFate
chosen
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
-
B.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
C.
eventualFate
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
D.
fateAfterSeparation
Indicates what ultimately happens to entities or their relationship after they have been separated.
-
E.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb518f7dc8190877997ea4cd3eed2 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.