Triple
T5060190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuddhadvaita Vedanta |
E114003
|
entity |
| Predicate | viewOfMaya |
P19250
|
FINISHED |
| Object | maya is the power of 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: maya is the power of God | Statement: [Shuddhadvaita Vedanta, viewOfMaya, maya is the power of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOfMaya Context triple: [Shuddhadvaita Vedanta, viewOfMaya, maya is the power of God]
-
A.
viewOnMatter
Indicates a stance, opinion, or perspective that one entity holds regarding a particular issue, topic, or matter.
-
B.
viewOfWill
Indicates a relationship where something represents, expresses, or reflects the will, intention, or volition of an agent.
-
C.
viewOver
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
-
D.
viewOnReality
chosen
Indicates a subject’s overarching perspective, interpretation, or conceptual stance regarding the nature of reality.
-
E.
viewOnCanon
Indicates that one entity expresses or embodies a particular stance, interpretation, or judgment about what is considered canonical within a given context.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7472a1dc8190942f568a81fdd961 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.