Triple
T898886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apocrypha (in early editions) |
E19403
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of the Bible |
C1842
|
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: section of the Bible Context triple: [Apocrypha (in early editions), instanceOf, section of the Bible]
-
A.
book section
A book section is a distinct, thematically cohesive subdivision of a book that groups related chapters or content under a common heading or purpose.
-
B.
division of the Old Testament
A division of the Old Testament is a major organizational section of the Hebrew Scriptures, such as the Law, the Prophets, or the Writings, that groups books by genre, authorship, or historical context.
-
C.
biblical text
A biblical text is a written work that forms part of the Bible, conveying religious narratives, laws, teachings, and poetry considered sacred and authoritative within Jewish and Christian traditions.
-
D.
biblical canon subdivision
chosen
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.
-
E.
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.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.