Triple
T27642332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reborn |
E696619
|
entity |
| Predicate | hasAfterlifeRealmName |
P63282
|
FINISHED |
| Object | Adystria |
—
|
NE NERFINISHED |
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: Adystria | Statement: [Reborn, hasAfterlifeRealmName, Adystria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAfterlifeRealmName Context triple: [Reborn, hasAfterlifeRealmName, Adystria]
-
A.
afterlifeName
chosen
Indicates the name or designation assigned to an entity in an afterlife or post-mortem context.
-
B.
hasAfterlifeElement
Indicates that something includes, depicts, or is associated with an element related to an afterlife or post-mortem existence.
-
C.
associatedAfterlife
Indicates a relationship where an entity is linked to, or characterized by, a particular concept, realm, or state of existence after death.
-
D.
afterlife
Indicates a relationship where an entity exists or experiences a state following physical death or the end of mortal life.
-
E.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:27 p.m.