Triple
T19160746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignatian corpus |
E469046
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early Christian text corpus |
C40625
|
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: early Christian text corpus Context triple: [Ignatian corpus, instanceOf, early Christian text corpus]
-
A.
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.
-
B.
patristic text collection
chosen
A patristic text collection is an organized compilation of writings by the early Christian Church Fathers, typically gathered for study, reference, or theological analysis.
-
C.
early Christian work
An early Christian work is a text or artifact produced by followers of Jesus in the first centuries CE that expresses, develops, or transmits emerging Christian beliefs, practices, and community life.
-
D.
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.
-
E.
Christian text tradition
The Christian text tradition is the historical process by which Christian writings—especially the Bible and related theological, liturgical, and devotional texts—are composed, transmitted, translated, interpreted, and canonized within Christian communities over time.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:06 p.m.