Triple
T18271613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European scholastic optics |
E437628
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval scientific tradition |
C39989
|
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 tradition Context triple: [European scholastic optics, instanceOf, medieval scientific tradition]
-
A.
medieval scientific work
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 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.
-
D.
question in history of science
A question in the history of science is an inquiry that examines how scientific ideas, practices, institutions, or technologies emerged, developed, and interacted with their broader historical and cultural contexts.
-
E.
history of science journal
A history of science journal is a scholarly periodical that publishes research articles, reviews, and essays examining the development of scientific ideas, practices, institutions, and their cultural contexts over time.
- F. None of above. chosen
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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.