Triple
T20202479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhavishya Parva |
E493258
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of a Sanskrit text |
C17235
|
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: section of a Sanskrit text Context triple: [Bhavishya Parva, instanceOf, section of a Sanskrit text]
-
A.
Sanskrit phrase
A Sanskrit phrase is a meaningful expression composed of one or more Sanskrit words, often carrying precise grammatical structure and layered philosophical or cultural significance.
-
B.
section of a religious text
chosen
A section of a religious text is a distinct, thematically or structurally defined subdivision—such as a chapter, verse group, or discourse unit—within a sacred scripture that conveys a coherent portion of its teachings or narrative.
-
C.
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.
-
D.
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.
-
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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:37 p.m.