Triple
T15148649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homiliary |
E361879
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval homiliary |
C17554
|
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 homiliary Context triple: [Homiliary, instanceOf, medieval homiliary]
-
A.
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.
-
B.
Old English homiletic collection
chosen
An Old English homiletic collection is a compiled set of sermons and religious teachings written in Old English, intended for use in preaching, instruction, and devotional reading in early medieval England.
-
C.
medieval church
A medieval church is a religious building from the Middle Ages, typically characterized by stone construction, vaulted ceilings, stained glass windows, and architectural styles such as Romanesque or Gothic, serving as a center for worship and community life.
-
D.
medieval legislation
Medieval legislation encompasses the body of laws, decrees, and legal customs established by monarchs, feudal lords, and religious authorities in Europe during the Middle Ages to regulate social order, property, crime, and governance.
-
E.
medieval charm
A medieval charm is a small, often inscribed object or spoken formula believed to harness supernatural or divine power for protection, healing, or influencing events in accordance with medieval beliefs and practices.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:07 a.m.