Triple
T20150565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ṭupṭīkā |
E491423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mīmāṃsā commentary |
C17526
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Mīmāṃsā commentary Context triple: [Ṭupṭīkā, instanceOf, Mīmāṃsā commentary]
-
A.
Mimamsa subtradition
chosen
The Mimamsa subtradition is a school of classical Indian philosophy focused on the exegesis of Vedic texts, emphasizing ritual action, linguistic analysis, and the authority of scripture as the primary means to dharma.
-
B.
Shaiva scripture commentary
A Shaiva scripture commentary is an interpretive text that explains, analyzes, and contextualizes sacred Shaiva scriptures, clarifying their philosophical, ritual, and devotional meanings for practitioners and scholars.
-
C.
Bhagavad Gita commentary
A Bhagavad Gita commentary is an interpretive work that explains, contextualizes, and analyzes the verses of the Bhagavad Gita to clarify their philosophical, spiritual, and practical meanings for readers.
-
D.
Kalpasūtra
Kalpasūtra is a Jain canonical text, primarily of the Śvetāmbara tradition, that contains biographies of the Tīrthaṅkaras (especially Mahāvīra), rules for monastic conduct, and liturgical guidelines recited during the Paryuṣaṇa festival.
-
E.
Mimamsa school
The Mimamsa school is an orthodox Hindu philosophical tradition that focuses on the exegesis of Vedic texts, emphasizing ritual action (karma), the authority of scripture, and the performance of duty as the primary means to uphold cosmic order and attain spiritual goals.
- F. None of above.
Provenance (1 batch)
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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
Created at: April 11, 2026, 11:33 p.m.