Triple
T29881706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sushruta Samhita |
E758895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ayurvedic medical text |
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: Ayurvedic medical text Context triple: [Sushruta Samhita, instanceOf, Ayurvedic medical text]
-
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.
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).
-
C.
Indian system of medicine
The Indian system of medicine is a holistic, traditional healthcare framework encompassing practices like Ayurveda, Siddha, Unani, Yoga, Naturopathy, and Homeopathy that emphasize balance of body, mind, and spirit using natural therapies and lifestyle regulation.
-
D.
Ayurvedic physician
An Ayurvedic physician is a healthcare practitioner who diagnoses and treats patients using the principles of traditional Indian medicine, emphasizing individualized balance of body, mind, and spirit through natural therapies, diet, and lifestyle.
-
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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:58 p.m.