Triple
T38280480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zakhireye Khwarazmshahi |
E1022068
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Persian medical text |
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 Persian medical text Context triple: [Zakhireye Khwarazmshahi, instanceOf, medieval Persian medical text]
-
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.
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.
-
E.
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.
- 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.