Triple
T23920319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tafsir al-Qur’an (Quranic commentaries) |
E602195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Shiʿi theological work |
C21595
|
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: Shiʿi theological work Context triple: [Tafsir al-Qur’an (Quranic commentaries), instanceOf, Shiʿi theological 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.
theological work
A theological work is a written or spoken scholarly exploration that systematically examines, interprets, and articulates beliefs about the nature of the divine, religious doctrines, and their implications for faith and practice.
-
C.
Islamic theological text
chosen
An Islamic theological text is a written work that systematically explores, explains, and defends Islamic beliefs about God, prophecy, revelation, and the unseen, often engaging with philosophical and doctrinal debates.
-
D.
doctrine in Shia Islam
Doctrine in Shia Islam is the structured set of theological beliefs, legal principles, and spiritual teachings that define Shia understanding of God, prophecy, Imamate, and religious practice.
-
E.
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.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 8:41 p.m.