Triple
T859261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puranas |
E18563
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu literature |
C1830
|
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: Hindu literature Context triple: [Puranas, instanceOf, Hindu literature]
-
A.
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.
-
B.
religious literature
chosen
Religious literature is a body of written works—such as scriptures, theological treatises, devotional texts, and spiritual narratives—created to express, interpret, and transmit the beliefs, practices, values, and experiences of a religious tradition.
-
C.
classical language of India
A classical language of India is an ancient, historically significant Indian language with a rich literary tradition and documented history over a long period, recognized for its cultural and scholarly importance.
-
D.
holy book
A holy book is a written text or collection of writings regarded by a religious community as divinely inspired or authoritative in matters of faith, morality, and spiritual practice.
-
E.
ancient Greek literature
Ancient Greek literature encompasses the epic, lyric, dramatic, historical, and philosophical writings produced in the Greek language from the archaic through the Hellenistic periods, foundational to Western literary and intellectual traditions.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.