Triple
T22799722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krishnavatara |
E564354
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian literature work |
C29223
|
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: Indian literature work Context triple: [Krishnavatara, instanceOf, Indian literature work]
-
A.
Indian literature
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.
-
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.
Kannada literary work
chosen
A Kannada literary work is a written creation—such as poetry, prose, drama, or criticism—composed in the Kannada language, reflecting its cultural, historical, and linguistic traditions.
-
D.
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.
-
E.
Punjabi literature
Punjabi literature is the body of written and oral works produced in the Punjabi language, encompassing poetry, prose, folklore, and religious texts that reflect the cultural, social, and historical experiences of Punjabi-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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:31 p.m.