Triple
T11111995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shantipurana |
E262778
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Indian literary work |
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: medieval Indian literary work Context triple: [Shantipurana, instanceOf, medieval Indian literary work]
-
A.
medieval literary work
A medieval literary work is a written or orally transmitted text from roughly the 5th to the 15th century that reflects the cultural, religious, and social contexts of the Middle Ages through genres such as epics, romances, hagiographies, chronicles, and lyric poetry.
-
B.
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.
-
C.
ancient literary work
An ancient literary work is a written composition created in antiquity that reflects the language, culture, beliefs, and artistic expression of early civilizations.
-
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.
Prakrit poetry collection
A Prakrit poetry collection is an anthology of verse composed in the Middle Indo-Aryan Prakrit languages, often featuring lyrical, romantic, and devotional themes that reflect classical Indian aesthetics and culture.
- 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:27 p.m.