Triple
T26322945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripura Upanishads |
E662165
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sanskrit religious text |
C22098
|
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: Sanskrit religious text Context triple: [Tripura Upanishads, instanceOf, Sanskrit religious text]
-
A.
Hindu religious texts
chosen
Hindu religious texts are a diverse body of ancient and medieval scriptures—including the Vedas, Upanishads, epics like the Mahabharata and Ramayana, and numerous Puranas and devotional works—that articulate Hindu philosophy, mythology, rituals, and ethical teachings.
-
B.
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.
-
C.
Zoroastrian religious text
A Zoroastrian religious text is a sacred writing that conveys the doctrines, rituals, hymns, and ethical teachings of the ancient Iranian religion founded by the prophet Zoroaster.
-
D.
Vedantic treatise
A Vedantic treatise is a systematic philosophical work that explicates, analyzes, and interprets the core metaphysical, epistemological, and spiritual doctrines of Vedanta, often through commentary on foundational scriptures like the Upanishads, Bhagavad Gita, and Brahma Sutras.
-
E.
Darshana text
A Darshana text is a traditional Indian philosophical treatise that systematically presents and defends the doctrines of a particular school of thought.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:29 p.m.