Triple
T19995173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Showings |
E494174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval religious work |
C12780
|
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 religious work Context triple: [Showings, instanceOf, medieval religious work]
-
A.
early medieval religious text
An early medieval religious text is a written work produced roughly between the 5th and 11th centuries that conveys, interprets, or codifies spiritual beliefs, practices, or doctrines within a particular religious tradition.
-
B.
medieval literary work
chosen
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.
-
C.
early medieval Christian text
An early medieval Christian text is a written work produced roughly between the 5th and 11th centuries that reflects and shapes Christian theology, liturgy, devotion, or ecclesiastical practice within the cultural and political contexts of early medieval Europe and the Mediterranean.
-
D.
Gospel book
A Gospel book is a handwritten or printed volume containing the text of one or more of the four canonical Christian Gospels, often richly decorated and used in liturgy and devotion.
-
E.
Gothic manuscript
A Gothic manuscript is a handwritten book or document produced in medieval Europe, characterized by dense, angular Gothic script, elaborate illumination, and often religious or legal content.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:31 p.m.