Triple
T29836110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashtanga Hridaya |
E757661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sanskrit medical treatise |
C52227
|
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 medical treatise Context triple: [Ashtanga Hridaya, instanceOf, Sanskrit medical treatise]
-
A.
Ayurvedic text
chosen
An Ayurvedic text is a traditional manuscript or written work that systematically presents the principles, practices, and remedies of Ayurveda for maintaining health and treating disease.
-
B.
Sanskrit and Prakrit scholastic works
Scholastic works in Sanskrit and Prakrit are learned treatises, commentaries, and systematic expositions that articulate, interpret, and debate religious, philosophical, grammatical, and literary traditions within classical South Asian intellectual culture.
-
C.
religious medical treatise
A religious medical treatise is a written work that integrates theological or spiritual beliefs with medical knowledge and practice, offering guidance on health, illness, and healing within a religious framework.
-
D.
Hindu astrological text
A Hindu astrological text is a traditional scripture or treatise that explains the principles, calculations, and interpretations of planetary positions and their influence on human life and events according to Hindu astrology (Jyotisha).
-
E.
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.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:37 p.m.