Triple
T35497887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitāb al-bāh |
E1025918
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Arabic medical treatise |
C61709
|
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 medical treatise Context triple: [Kitāb al-bāh, instanceOf, medieval Arabic medical treatise]
-
A.
medieval medical treatise
chosen
A medieval medical treatise is a written work from the Middle Ages that compiles contemporary medical knowledge, theories, remedies, and practices, often blending classical sources, religious beliefs, and empirical observations.
-
B.
ancient medical treatise
An ancient medical treatise is a historical written work that systematically records contemporary medical knowledge, theories, and treatments, often blending empirical observations with philosophical or religious beliefs.
-
C.
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.
-
D.
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.
-
E.
Islamic medical work
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.
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.