Triple
T11122064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kannada literature |
E263040
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional literature of India |
C25344
|
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: regional literature of India Context triple: [Kannada literature, instanceOf, regional literature of India]
-
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.
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.
-
C.
regional literary tradition
chosen
A regional literary tradition is the body of written and oral works, styles, themes, and narrative practices that emerge from and reflect the history, culture, and linguistic characteristics of a specific geographic area.
-
D.
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.
-
E.
Indian literary award
An Indian literary award is a formal recognition conferred in India to honor outstanding contributions to literature across various languages, genres, and forms.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:28 p.m.