Triple
T26926168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charaka Samhita |
E677783
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ayurvedic 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 text Context triple: [Charaka Samhita, instanceOf, Ayurvedic text]
-
A.
Darshana text
A Darshana text is a traditional Indian philosophical treatise that systematically presents and defends the doctrines of a particular school of thought.
-
B.
Samkhya text
A Samkhya text is a philosophical work rooted in the ancient Indian Samkhya system that systematically analyzes reality through the dual principles of purusha (consciousness) and prakriti (primordial matter) to explain cosmology, psychology, and liberation.
-
C.
Hindu religious texts
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.
-
D.
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.
-
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. 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 6:09 a.m.