Triple
T13131809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitab al-Ma‘rifa bi al-Hiyal al-Handasiyya |
E311981
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval scientific treatise |
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 treatise Context triple: [Kitab al-Ma‘rifa bi al-Hiyal al-Handasiyya, instanceOf, medieval scientific treatise]
-
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.
Renaissance treatise
A Renaissance treatise is a systematic, often humanist-influenced written work from roughly the 14th to 17th centuries that explores a specific subject—such as art, science, politics, or philosophy—through structured argument and scholarly discourse.
-
D.
section of a scientific treatise
A section of a scientific treatise is a logically bounded subdivision that develops a specific aspect of the overall argument or topic through structured exposition, evidence, and analysis.
-
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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:08 p.m.