Triple
T38664330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dasam Bani |
E940412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sikh religious scripture |
C44442
|
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: Sikh religious scripture Context triple: [Dasam Bani, instanceOf, Sikh religious scripture]
-
A.
central scripture of Sikhism
The central scripture of Sikhism, the Guru Granth Sahib, is a sacred compilation of hymns and teachings by Sikh Gurus and other saints that serves as the eternal living Guru and spiritual guide for Sikhs.
-
B.
Sikh religious literature
chosen
Sikh religious literature encompasses the sacred scriptures, hymns, commentaries, and historical writings that articulate Sikh theology, ethics, devotional practice, and community identity, centered on the Guru Granth Sahib and related texts.
-
C.
Sikh scripture composition
A Sikh scripture composition is a sacred poetic hymn or verse, authored by Sikh Gurus or other revered saints, that conveys spiritual teachings, ethical guidance, and devotional praise, and is preserved within the Sikh scriptural tradition.
-
D.
Sikh religious concept
A Sikh religious concept is a fundamental idea or principle within Sikhism—such as belief in one formless God, the teachings of the Gurus, or practices like seva and simran—that shapes the faith’s theology, ethics, and way of life.
-
E.
Sikh prayer portion
A Sikh prayer portion is a distinct section of Sikh liturgical recitation, often drawn from the Guru Granth Sahib or other approved scriptures, used for daily devotion, ceremonial observances, or specific spiritual intentions.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:33 p.m.