Triple
T21908023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siddhānta-kaumudī |
E540989
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sanskrit grammatical treatise |
C43672
|
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: Sanskrit grammatical treatise Context triple: [Siddhānta-kaumudī, instanceOf, Sanskrit grammatical treatise]
-
A.
work on Sanskrit grammar
chosen
A systematic body of scholarly activity focused on analyzing, interpreting, and teaching the rules, structures, and usage patterns of the Sanskrit language.
-
B.
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.
-
C.
Vedic exegesis work
A Vedic exegesis work is a scholarly text that interprets, analyzes, and explains the meanings, rituals, and philosophical doctrines of the Vedas within their linguistic, historical, and theological contexts.
-
D.
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.
-
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_69e0c47b4e8c81908c8076eaa4c8e4f2 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:39 p.m.