Triple
T19308257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De visione voce auditu |
E482898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance medical text |
C15266
|
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: Renaissance medical text Context triple: [De visione voce auditu, instanceOf, Renaissance medical text]
-
A.
Renaissance treatise
chosen
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.
-
B.
religious medical treatise
A religious medical treatise is a written work that integrates theological or spiritual beliefs with medical knowledge and practice, offering guidance on health, illness, and healing within a religious framework.
-
C.
Renaissance literature work
A Renaissance literature work is a written piece, typically from the 14th to 17th centuries, that reflects the era’s revival of classical learning, humanist ideals, and experimentation with new literary forms and vernacular languages.
-
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.
17th-century book
A 17th-century book is a bound collection of printed or handwritten pages produced between 1601 and 1700, reflecting the period’s materials, typography, and intellectual, religious, or political culture.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:32 p.m.