Triple
T32547243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian–Muslim disputations |
E831878
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval literature genre |
C17982
|
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 literature genre Context triple: [Christian–Muslim disputations, instanceOf, medieval literature genre]
-
A.
medieval literary work
A medieval literary work is a written or orally transmitted text from roughly the 5th to the 15th century that reflects the cultural, religious, and social contexts of the Middle Ages through genres such as epics, romances, hagiographies, chronicles, and lyric poetry.
-
B.
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.
-
C.
medieval literary movement
chosen
A medieval literary movement is a historically situated trend or school of writing in the Middle Ages characterized by shared themes, styles, and cultural or religious influences that shaped the production and reception of texts.
-
D.
Arthurian literature
Arthurian literature encompasses the body of medieval and later stories, poems, and romances centered on King Arthur, his knights, and the mythical world of Camelot.
-
E.
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.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:02 a.m.