Triple
T19103206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaitanya Mangala |
E467586
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bengali religious text |
C22098
|
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: Bengali religious text Context triple: [Chaitanya Mangala, instanceOf, Bengali religious text]
-
A.
Hindu religious texts
chosen
Hindu religious texts are a diverse body of ancient and medieval scriptures—including the Vedas, Upanishads, epics like the Mahabharata and Ramayana, and numerous Puranas and devotional works—that articulate Hindu philosophy, mythology, rituals, and ethical teachings.
-
B.
Bengali poetry collection
A Bengali poetry collection is an anthology of poems written in the Bengali language, often reflecting the region’s cultural, emotional, and philosophical themes across various poets or a single poet’s body of work.
-
C.
Tibetan Buddhist text collection
A Tibetan Buddhist text collection is an organized compilation of canonical and commentarial writings—such as sutras, tantras, philosophical treatises, and ritual manuals—preserved in Tibetan language and script for study, practice, and transmission of the Buddhist tradition.
-
D.
Shingon Buddhist text
A Shingon Buddhist text is a written work that conveys the doctrines, rituals, esoteric teachings, and liturgical practices of the Shingon school of Japanese Vajrayana Buddhism.
-
E.
Hindi-language book
A Hindi-language book is a written work in which the primary text is composed in the Hindi language, typically using the Devanagari script, intended for reading by Hindi-speaking audiences.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:04 p.m.