Triple
T4781803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanva Shakha |
E106383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu scriptural tradition |
C5711
|
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: Hindu scriptural tradition Context triple: [Kanva Shakha, instanceOf, Hindu scriptural tradition]
-
A.
Sanskrit literature
Sanskrit literature is the body of classical and post-classical writings in the Sanskrit language, encompassing religious scriptures, epic poetry, drama, philosophy, science, and aesthetics that shaped much of South Asian intellectual and cultural history.
-
B.
Hindu denomination
chosen
A Hindu denomination is a distinct religious tradition within Hinduism characterized by shared beliefs, practices, scriptures, and devotional focus, often centered on a particular deity or philosophical school.
-
C.
denomination of Hinduism
A denomination of Hinduism is a distinct religious tradition within Hinduism characterized by its own set of core deities, philosophies, rituals, and community practices while still sharing the broader Hindu cultural and scriptural framework.
-
D.
religious tradition
A religious tradition is an enduring, socially shared system of beliefs, practices, narratives, and institutions that shapes how a community understands and relates to the sacred, the moral order, and ultimate meaning.
-
E.
classical language of India
A classical language of India is an ancient, historically significant Indian language with a rich literary tradition and documented history over a long period, recognized for its cultural and scholarly importance.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:22 p.m.