Triple
T19963273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viradha |
E479867
|
entity |
| Predicate | achievesAfterDeath |
P126199
|
FINISHED |
| Object | release from curse |
—
|
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: release from curse | Statement: [Viradha, achievesAfterDeath, release from curse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievesAfterDeath Context triple: [Viradha, achievesAfterDeath, release from curse]
-
A.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
B.
completionAfterDeathOf
Indicates that one event, process, or work is completed only after the death of a specified person.
-
C.
afterDeathOf
chosen
Indicates that one event, state, or condition occurs subsequent to and as a result of the death of a specified entity.
-
D.
continuedAfterDeathOf
Indicates that an action, state, or process persisted beyond and despite the death of a specified entity.
-
E.
releasedAfterDeathOf
Indicates that something (such as a work, product, or announcement) was released only after the death of a specified person.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af619108190825cbcfb6b8e1fa5 |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.