Triple
T38314795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibn al-Quff |
E1033793
|
entity |
| Predicate | usedMedicalTradition |
P108232
|
FINISHED |
| Object | Galenic medicine |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Galenic medicine | Statement: [Ibn al-Quff, usedMedicalTradition, Galenic medicine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMedicalTradition Context triple: [Ibn al-Quff, usedMedicalTradition, Galenic medicine]
-
A.
practicedMedicineOfTradition
chosen
Indicates that an entity engaged in the medical practices or healing methods associated with a particular cultural or traditional system.
-
B.
traditionalUse
Indicates that something is used or practiced according to long-established customs, habits, or cultural traditions.
-
C.
languageOfTraditionalUse
Indicates the language traditionally used or associated with a given entity, such as a work, practice, or community.
-
D.
hasUseInTradition
Indicates that something is employed or holds a functional role within a particular cultural, religious, or historical tradition.
-
E.
medicinalUse
Indicates that one entity is used as a treatment or remedy for a disease, condition, or health-related purpose affecting another entity.
- F. None of above.
Provenance (3 batches)
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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.