Triple
T17936921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamasutra |
E448491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | classical Sanskrit literature |
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: classical Sanskrit literature Context triple: [Kamasutra, instanceOf, classical Sanskrit literature]
-
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.
classical Tamil literature
Classical Tamil literature encompasses the ancient poetic, philosophical, and didactic works composed primarily between 300 BCE and 300 CE in Tamil, including the Sangam corpus and later ethical and devotional texts that shaped South Indian culture and thought.
-
C.
classical literature
Classical literature encompasses the enduring works of ancient Greek and Roman authors, as well as later canonical texts, that have significantly shaped Western thought, art, and literary tradition.
-
D.
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.
-
E.
ancient literature
Ancient literature encompasses the written works, myths, epics, religious texts, and philosophical writings produced by early civilizations that reveal their cultures, beliefs, and historical experiences.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:21 a.m.