Triple
T25693324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenkalai |
E644253
|
entity |
| Predicate | hasViewOnLiberation |
P22619
|
FINISHED |
| Object | moksha granted solely by God’s will |
—
|
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: moksha granted solely by God’s will | Statement: [Tenkalai, hasViewOnLiberation, moksha granted solely by God’s will]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewOnLiberation Context triple: [Tenkalai, hasViewOnLiberation, moksha granted solely by God’s will]
-
A.
viewOnLiberation
chosen
Indicates a stance, opinion, or perspective that an entity holds regarding the concept, process, or outcomes of liberation.
-
B.
liberationEvent
Indicates an event in which an entity is freed from control, confinement, or oppression by another entity or condition.
-
C.
liberationAchievedBy
Indicates that a state of liberation or freedom is brought about or attained through a specific action, process, or agent.
-
D.
liberationDate
Indicates the date on which an entity was freed, released, or liberated from a prior state of control, confinement, or oppression.
-
E.
viewOnLiberty
Indicates a person's stance, opinion, or perspective regarding the concept or principles of liberty.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 8:31 p.m.