Triple
T19963232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabandha |
E479866
|
entity |
| Predicate | fateAfterLiberation |
P3146
|
FINISHED |
| Object | ascends to higher realms |
—
|
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: ascends to higher realms | Statement: [Kabandha, fateAfterLiberation, ascends to higher realms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateAfterLiberation Context triple: [Kabandha, fateAfterLiberation, ascends to higher realms]
-
A.
fate
chosen
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
B.
liberationAchievedBy
Indicates that a state of liberation or freedom is brought about or attained through a specific action, process, or agent.
-
C.
liberatedCity
Indicates that an agent has freed a city from control, occupation, or oppression.
-
D.
liberationEvent
Indicates an event in which an entity is freed from control, confinement, or oppression by another entity or condition.
-
E.
fateInSequel
Indicates that the outcome or destiny of an entity is revealed or occurs in a subsequent work, installment, or sequel.
- 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.