Triple
T16940431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitab al-Kimya |
E410935
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval scientific text |
C28473
|
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 scientific text Context triple: [Kitab al-Kimya, instanceOf, medieval scientific text]
-
A.
medieval scientific work
chosen
A medieval scientific work is a scholarly text produced between roughly the 5th and 15th centuries that investigates natural phenomena using the philosophical, religious, and observational frameworks of its time.
-
B.
medieval scientist
A medieval scientist is a scholar who investigates natural phenomena using observation, experimentation, and philosophical reasoning within the intellectual, religious, and technological constraints of the Middle Ages.
-
C.
medieval prose text
A medieval prose text is a written work from the Middle Ages composed in continuous, non-verse form, often preserving narratives, religious teachings, legal codes, or historical accounts in the vernacular or Latin.
-
D.
medieval literary work
A medieval literary work is a written or orally transmitted text from roughly the 5th to the 15th century that reflects the cultural, religious, and social contexts of the Middle Ages through genres such as epics, romances, hagiographies, chronicles, and lyric poetry.
-
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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.