Triple
T28983929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhavisayattakaha |
E734626
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indo-Aryan literary work |
C18850
|
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: Indo-Aryan literary work Context triple: [Bhavisayattakaha, instanceOf, Indo-Aryan literary work]
-
A.
Sindhi literary work
A Sindhi literary work is a creative or scholarly text composed in the Sindhi language that reflects the culture, history, values, and expressive traditions of Sindhi-speaking communities.
-
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.
Sanskrit literary style
Sanskrit literary style is a highly structured and ornate mode of expression characterized by precise grammar, rich metaphor, layered wordplay, and codified aesthetic principles (alaṅkāra and rasa) used in classical Indian literature.
-
D.
Indian literature
chosen
Indian literature encompasses the diverse body of written and oral works produced in the many languages of the Indian subcontinent, reflecting its rich cultural, religious, and historical traditions from ancient times to the present.
-
E.
Telugu literary work
A Telugu literary work is a written creation composed in the Telugu language, encompassing genres such as poetry, prose, drama, and criticism that reflect the culture, history, and aesthetics of Telugu-speaking communities.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 9:13 a.m.