Triple
T25693326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenkalai |
E644253
|
entity |
| Predicate | hasViewOnJiva |
P57092
|
FINISHED |
| Object | soul as utterly dependent on God |
—
|
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: soul as utterly dependent on God | Statement: [Tenkalai, hasViewOnJiva, soul as utterly dependent on God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewOnJiva Context triple: [Tenkalai, hasViewOnJiva, soul as utterly dependent on God]
-
A.
viewOnJiva
chosen
Indicates a perspective, opinion, or conceptual stance that one entity holds regarding the concept or entity referred to as "Jiva."
-
B.
hasViewOnIndividuation
Indicates that one entity holds a particular theory, stance, or interpretation regarding the process or concept of individuation.
-
C.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
D.
hasParticularView
Indicates that one entity holds, expresses, or is characterized by a specific opinion, perspective, or standpoint regarding something.
-
E.
hasViewOnLakshmi
Indicates that an entity holds an opinion, perspective, or stance regarding Lakshmi.
- 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_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 8:31 p.m.