Triple
T20964624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katha Shakha |
E516334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu religious text tradition |
C22098
|
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 religious text tradition Context triple: [Katha Shakha, instanceOf, Hindu religious text tradition]
-
A.
Hindu religious texts
chosen
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.
-
B.
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.
-
C.
place in Hindu tradition
A place in Hindu tradition is a physical or sacred location—such as a temple, pilgrimage site, river, mountain, or city—imbued with religious, mythological, or spiritual significance and associated rituals.
-
D.
Hindu reformist text
A Hindu reformist text is a written work that critiques existing religious practices and beliefs within Hinduism and advocates changes to align them with contemporary ethical, social, or rational ideals.
-
E.
Hindu monastic tradition
A Hindu monastic tradition is an organized lineage or order of renunciants who adopt vows of celibacy, simplicity, and spiritual discipline to pursue liberation and preserve and transmit Hindu philosophical, ritual, and ethical teachings.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 1:32 p.m.