Triple
T5782768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindu scriptures |
E128199
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu religious text corpus |
C1770
|
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 corpus Context triple: [Hindu scriptures, instanceOf, Hindu religious text corpus]
-
A.
Sanskrit literature
chosen
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.
Shaivite scripture
A Shaivite scripture is a sacred Hindu text that centers on the worship, mythology, philosophy, and rituals associated with the god Shiva and his manifestations.
-
C.
religious text carrier
A religious text carrier is an entity (person, object, or medium) that transports, preserves, or conveys sacred writings from one place, time, or audience to another.
-
D.
Shaiva scripture commentary
A Shaiva scripture commentary is an interpretive text that explains, analyzes, and contextualizes sacred Shaiva scriptures, clarifying their philosophical, ritual, and devotional meanings for practitioners and scholars.
-
E.
holy book
A holy book is a written text or collection of writings regarded by a religious community as divinely inspired or authoritative in matters of faith, morality, and spiritual practice.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:50 p.m.