Triple
T7375400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishkat al-Anwar |
E170110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persianate Islamic text |
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: Persianate Islamic text Context triple: [Mishkat al-Anwar, instanceOf, Persianate Islamic text]
-
A.
Middle Persian text
A Middle Persian text is a written work composed in the Middle Iranian language of the Sasanian and early Islamic periods, typically preserved in Pahlavi script or related writing systems.
-
B.
Islamic theological text
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.
Mandaean legal-theological text
A Mandaean legal-theological text is a written work that codifies religious laws, rituals, and doctrinal teachings within the Mandaean faith, guiding both communal practice and spiritual belief.
-
D.
classical Arabic text
A classical Arabic text is a written work composed in the formal, literary variety of Arabic used from the early Islamic period through the medieval era, characterized by rich rhetoric, precise grammar, and adherence to traditional stylistic norms.
-
E.
Judeo-Arabic work
A Judeo-Arabic work is a text written in Arabic using Hebrew script, typically produced by Jewish communities in the medieval Islamic world for religious, philosophical, or everyday purposes.
- F. None of above. chosen
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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:07 p.m.