Triple
T17648586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sirr-i-Akbar |
E429425
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Islamic–Hindu comparative work |
C22096
|
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: Islamic–Hindu comparative work Context triple: [Sirr-i-Akbar, instanceOf, Islamic–Hindu comparative work]
-
A.
Sunni Islamic jurisprudence work
A Sunni Islamic jurisprudence work is a scholarly text that systematically presents, interprets, and applies Islamic legal rulings and principles according to one or more Sunni schools of law.
-
B.
classical Islamic work
A classical Islamic work is a foundational text produced in the formative and medieval periods of Islamic civilization that systematically presents, interprets, or preserves religious, legal, philosophical, or literary knowledge within the Islamic tradition.
-
C.
Shaiva scripture commentary
A Shaiva scripture commentary is an interpretive text that explains, analyzes, and contextualizes sacred Shaiva scriptures, clarifying their philosophical, ritual, and devotional meanings for practitioners and scholars.
-
D.
Hindu reformist text
A Hindu reformist text is a written work that critiques existing religious practices and beliefs within Hinduism and advocates changes to align them with contemporary ethical, social, or rational ideals.
-
E.
Persianate Islamic text
chosen
A Persianate Islamic text is a written work produced within the cultural sphere shaped by Persian language, literary norms, and aesthetics that engages with Islamic religious, philosophical, legal, or mystical themes.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 6:05 a.m.