Triple
T38281281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Mansuri fi al-tibb |
E1022086
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval medical compendium |
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 medical compendium Context triple: [Al-Mansuri fi al-tibb, instanceOf, medieval medical compendium]
-
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.
medieval physician
A medieval physician is a learned healer who diagnoses and treats illness using humoral theory, herbal remedies, and limited empirical observation within the social and religious framework of the Middle Ages.
-
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.
medical compendium
A medical compendium is a comprehensive, systematically organized reference work that consolidates medical knowledge, including diseases, treatments, diagnostics, and related scientific information, for use by healthcare professionals and students.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.