Triple
T13131091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman medicine |
E311967
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient medicine tradition |
C13043
|
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: ancient medicine tradition Context triple: [Roman medicine, instanceOf, ancient medicine tradition]
-
A.
historical medical system
chosen
A historical medical system is an organized body of theories, practices, and institutions used in the past to understand, diagnose, and treat illness within a particular cultural and scientific context.
-
B.
Indian system of medicine
The Indian system of medicine is a holistic, traditional healthcare framework encompassing practices like Ayurveda, Siddha, Unani, Yoga, Naturopathy, and Homeopathy that emphasize balance of body, mind, and spirit using natural therapies and lifestyle regulation.
-
C.
alternative medicine
Alternative medicine is a broad range of health care practices, products, and therapies that are not typically part of conventional Western medical training or standard clinical practice, often emphasizing holistic, natural, or traditional approaches to healing.
-
D.
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.
-
E.
semi-divine physicians
Semi-divine physicians are healer figures who straddle the boundary between mortal and divine, wielding supernatural or sacred medical knowledge to cure ailments and restore balance.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:07 p.m.