Triple
T17589663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharh al-Qanun |
E428410
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Islamic medical text |
C32510
|
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: Islamic medical text Context triple: [Sharh al-Qanun, instanceOf, Islamic medical text]
-
A.
Islamic medical literature
Islamic medical literature encompasses the diverse body of medical writings produced in the Islamic world, integrating Greco-Roman, Persian, Indian, and original Islamic medical knowledge into systematic texts on theory, practice, pharmacology, and ethics.
-
B.
Islamic medical work
chosen
An Islamic medical work is a scholarly text produced within the Islamic world that integrates Greco-Arabic medical knowledge with religious, philosophical, and practical insights to diagnose, treat, and prevent illness.
-
C.
religious medical treatise
A religious medical treatise is a written work that integrates theological or spiritual beliefs with medical knowledge and practice, offering guidance on health, illness, and healing within a religious framework.
-
D.
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.
-
E.
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.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:51 a.m.