Triple
T18272969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitab al-Sirr al-Asrar |
E437659
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Arabic alchemical text |
C38277
|
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: medieval Arabic alchemical text Context triple: [Kitab al-Sirr al-Asrar, instanceOf, medieval Arabic alchemical text]
-
A.
alchemical treatise
chosen
An alchemical treatise is a written work that systematically explores the theories, practices, symbols, and philosophical underpinnings of alchemy, often blending practical recipes with mystical or spiritual interpretations of transformation.
-
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.
Lurianic Kabbalah text
A Lurianic Kabbalah text is a work that presents, explains, or elaborates on the mystical doctrines of Rabbi Isaac Luria, focusing on concepts such as tzimtzum (divine contraction), shevirat ha-kelim (shattering of the vessels), and tikkun (cosmic repair).
-
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.
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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.