Triple
T3742834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masorah |
E79741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biblical tradition |
C331
|
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: biblical tradition Context triple: [Masorah, instanceOf, biblical tradition]
-
A.
New Testament tradition
New Testament tradition is the body of interpretive practices, teachings, and communal memories through which Christian communities have transmitted, received, and reshaped the writings and theology of the New Testament across history.
-
B.
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.
-
C.
religious tradition
chosen
A religious tradition is an enduring, socially shared system of beliefs, practices, narratives, and institutions that shapes how a community understands and relates to the sacred, the moral order, and ultimate meaning.
-
D.
biblical theology
Biblical theology is the disciplined study of the progressive revelation, themes, and theology of the Bible as they unfold within their historical and literary contexts across the canon.
-
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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:34 p.m.