Triple
T3852746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Orations Against the Arians |
E85335
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian theological discourse |
C5743
|
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 theological discourse Context triple: [Four Orations Against the Arians, instanceOf, Christian theological discourse]
-
A.
Christian doctrine
Christian doctrine is the organized body of beliefs and teachings derived from the Bible and Christian tradition that defines the faith’s understanding of God, salvation, morality, and the church.
-
B.
theological work
chosen
A theological work is a written or spoken scholarly exploration that systematically examines, interprets, and articulates beliefs about the nature of the divine, religious doctrines, and their implications for faith and practice.
-
C.
Christian belief
Christian belief is a faith-centered worldview grounded in the life, teachings, death, and resurrection of Jesus Christ, affirming salvation through Him and guiding moral, spiritual, and communal practices based on the Bible.
-
D.
Christian religious observance
Christian religious observance is the practice of worship, rituals, and disciplines—such as prayer, sacraments, and holy days—through which Christians express devotion to God and live out their faith in community and daily life.
-
E.
Biblical discourse
Biblical discourse is the structured communication—spoken, written, or interpretive—that engages with, explains, or applies the texts, themes, and theology of the Bible within specific historical, cultural, and religious contexts.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.