Triple
T25857572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter of Toledo |
E651390
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval translator |
C50806
|
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 translator Context triple: [Peter of Toledo, instanceOf, medieval translator]
-
A.
medieval Jewish translator
A medieval Jewish translator is a scholar who rendered religious, philosophical, scientific, or literary works between Hebrew, Arabic, Latin, and vernacular languages, facilitating intellectual exchange across Jewish and broader medieval cultures.
-
B.
medieval translator family
A medieval translator family is a lineage of individuals in the Middle Ages dedicated to translating texts—often religious, philosophical, or scientific—across languages such as Latin, Arabic, Greek, and vernacular tongues, thereby preserving and transmitting knowledge across cultures and generations.
-
C.
medievalist
A medievalist is a scholar or enthusiast who studies and interprets the history, culture, literature, and societies of the Middle Ages.
-
D.
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.
-
E.
medieval commentary
A medieval commentary is a scholarly work from the Middle Ages that explains, interprets, and elaborates on an authoritative text, often blending exposition with theological, philosophical, or legal analysis.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:01 a.m.