Triple
T34076725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakkar K |
E873925
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sikh religious article of faith |
C28734
|
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 article of faith Context triple: [Kakkar K, instanceOf, Sikh religious article of faith]
-
A.
Sikh article of faith
chosen
A Sikh article of faith is a mandated religious symbol or practice, such as the Five Ks, that embodies core Sikh beliefs, identity, and commitment to spiritual and moral discipline.
-
B.
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.
-
C.
symbol of Sikhism
The symbol of Sikhism, known as the Khanda, is a composite emblem featuring a double-edged sword flanked by two curved kirpans and encircled by a chakkar, representing divine knowledge, spiritual and temporal authority, and the unity of God.
-
D.
Sikh religious festival
A Sikh religious festival is a communal celebration that commemorates significant events in Sikh history and spirituality through prayer, scripture recitation, kirtan (devotional singing), and shared meals (langar) at gurdwaras and in the wider community.
-
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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:52 a.m.