Triple
T33647189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medieval Lives of Saint George |
E861990
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval text tradition |
C1507
|
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 text tradition Context triple: [Medieval Lives of Saint George, instanceOf, medieval text tradition]
-
A.
Anglo-Norman manuscript tradition
The Anglo-Norman manuscript tradition encompasses the body of texts written in Anglo-Norman French in medieval England, preserved and transmitted through manuscripts that reflect the linguistic, cultural, and political interplay between Norman and English societies from the 11th to the 15th centuries.
-
B.
medieval prose text
chosen
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.
-
C.
Biblical manuscript tradition
The biblical manuscript tradition encompasses the historical transmission, copying, preservation, and variation of biblical texts across languages, regions, and centuries.
-
D.
medieval literary language
Medieval literary language is the stylized, often highly formal written register of Middle Ages texts, shaped by manuscript culture, regional dialects, and genre-specific conventions distinct from everyday speech.
-
E.
medieval translator
A medieval translator is a scholar who converts texts between languages of the Middle Ages, navigating historical dialects, cultural contexts, and often religious or legal nuances to preserve meaning across linguistic boundaries.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.