Triple
T1237590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic biblical canon |
E26582
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian canon |
C609
|
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 canon Context triple: [Roman Catholic biblical canon, instanceOf, Christian canon]
-
A.
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.
-
B.
biblical canon subdivision
A biblical canon subdivision is a distinct grouping or category within the collection of authoritative biblical books, such as the Pentateuch, Historical Books, Prophets, Gospels, or Epistles.
-
C.
biblical canon division
A biblical canon division is a conceptual grouping that categorizes the books of the Bible into distinct sections (such as Law, Prophets, Writings, Gospels, Epistles) according to religious tradition and theological function.
-
D.
Biblical manuscript tradition
The biblical manuscript tradition encompasses the historical transmission, copying, preservation, and variation of biblical texts across languages, regions, and centuries.
-
E.
religious scripture
chosen
A religious scripture is a revered written text or collection of texts that a faith community regards as divinely inspired or authoritative in matters of belief, morality, and spiritual practice.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
Created at: March 1, 2026, 7:47 p.m.