Triple
T17290186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Giants |
E419763
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish pseudepigraphon |
C36514
|
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: Jewish pseudepigraphon Context triple: [Book of Giants, instanceOf, Jewish pseudepigraphon]
-
A.
apocryphal book
An apocryphal book is a work of uncertain or disputed authorship or canonical status, often associated with religious traditions but not officially accepted into the standard scriptural canon.
-
B.
Old Testament apocrypha
Old Testament apocrypha are a collection of ancient Jewish writings, not included in the Hebrew Bible, that expand upon or supplement Old Testament narratives and teachings and are considered canonical by some Christian traditions but not by others.
-
C.
Jewish apocalyptic work
chosen
A Jewish apocalyptic work is a religious text, typically from the Second Temple period, that reveals divine mysteries about the end of days, cosmic conflict, and ultimate judgment through symbolic visions and angelic mediators.
-
D.
Lurianic Kabbalah text
A Lurianic Kabbalah text is a work that presents, explains, or elaborates on the mystical doctrines of Rabbi Isaac Luria, focusing on concepts such as tzimtzum (divine contraction), shevirat ha-kelim (shattering of the vessels), and tikkun (cosmic repair).
-
E.
apocryphal gospel
An apocryphal gospel is a non-canonical early Christian text, often narrating the life or teachings of Jesus, that was excluded from the official New Testament and typically regarded as of doubtful or disputed authenticity.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:40 a.m.