Triple
T5562343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longer Rules |
E145793
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian monastic text |
C17548
|
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: Christian monastic text Context triple: [Longer Rules, instanceOf, Christian monastic text]
-
A.
early medieval Christian text
chosen
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.
Christian monastics
Christian monastics are individuals who dedicate their lives to God through vows such as poverty, chastity, and obedience, living in communities or solitude according to specific religious rules and traditions.
-
C.
Orthodox Christian treatise
An Orthodox Christian treatise is a formal written work that systematically explains, defends, or reflects upon the doctrines, spiritual life, and liturgical practices of the Eastern Orthodox Church in light of Scripture and Holy Tradition.
-
D.
patristic text
A patristic text is a written work authored by an early Christian theologian or Church Father, typically from the first to eighth centuries, that contributes to the development of Christian doctrine, exegesis, and pastoral teaching.
-
E.
Christian liturgical text
A Christian liturgical text is a written work used in worship services that provides structured prayers, readings, and rituals guiding communal and individual devotion.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:36 p.m.