Triple

T30091341
Position Surface form Disambiguated ID Type / Status
Subject al-Arbaʿīn fī Uṣūl al-Dīn E764741 entity
Predicate instanceOf P0 FINISHED
Object Ashʿarī 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: Ashʿarī theological work
Context triple: [al-Arbaʿīn fī Uṣūl al-Dīn, instanceOf, Ashʿarī theological work]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. Mu'tazilite theologian
    A Mu'tazilite theologian is a medieval Islamic scholar who upholds the primacy of reason in theology, emphasizing divine justice, human free will, and the created nature of the Qur’an.
  • E. 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.
  • 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_69f22473c0fc8190a926a8051b3b378b completed April 29, 2026, 3:32 p.m.
Created at: April 29, 2026, 7:06 p.m.