Triple
T26066420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirror of Holy Church |
E657415
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval instructional text |
C45508
|
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 instructional text Context triple: [Mirror of Holy Church, instanceOf, medieval instructional text]
-
A.
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.
-
B.
medieval pedagogical tool
chosen
A medieval pedagogical tool is an instructional object or method—such as manuscripts, mnemonic diagrams, abacuses, or didactic religious imagery—used in the Middle Ages to facilitate learning, memory, and moral or scholarly instruction.
-
C.
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.
-
D.
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.
-
E.
medieval library
A medieval library is a collection of handwritten manuscripts and scrolls, often housed in monasteries or universities, where texts are preserved, copied, and studied under strict custodial and scholarly traditions.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:24 p.m.