Triple
T20150567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ṭupṭīkā |
E491423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vedic exegesis work |
C43039
|
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: Vedic exegesis work Context triple: [Ṭupṭīkā, instanceOf, Vedic exegesis work]
-
A.
Vedic scholastic lineage
A Vedic scholastic lineage is a continuous tradition of teachers and disciples dedicated to preserving, interpreting, and transmitting Vedic scriptures, rituals, and philosophical doctrines across generations.
-
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.
Hindu astronomical work
A Hindu astronomical work is a traditional Indian text that systematically describes celestial bodies, their motions, and related mathematical and calendrical calculations within the framework of Hindu cosmology.
-
D.
Hindu technical scripture
A Hindu technical scripture is a specialized sacred text that systematically presents practical knowledge—such as ritual procedures, architecture, arts, sciences, or governance—within a Hindu religious and philosophical framework.
-
E.
Persian translation of the Upanishads
A Persian translation of the Upanishads is a rendered version of these foundational Hindu philosophical scriptures into the Persian language, aiming to convey their spiritual teachings, metaphysical concepts, and poetic nuances to Persian-speaking readers.
- F. None of above. chosen
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.