Triple
T22188009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Da'a'im al-Islam |
E548345
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Isma'ili doctrinal text |
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: Isma'ili doctrinal text Context triple: [Da'a'im al-Islam, instanceOf, Isma'ili doctrinal text]
-
A.
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.
-
B.
Persianate Islamic text
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.
-
C.
Manichaean religious text
A Manichaean religious text is a written work that conveys the dualistic doctrines, cosmology, ethics, and ritual practices of the Manichaean faith, often framed as revelations or teachings from Mani and other divine figures.
-
D.
Islamic literary work
An Islamic literary work is a written composition—such as scripture, exegesis, poetry, theology, law, or devotional prose—rooted in Islamic beliefs, history, and culture, often engaging with the Qur’an, Hadith, and related religious or intellectual traditions.
-
E.
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.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:35 p.m.