Triple
T30472485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quintuplex Psalterium |
E775342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biblical edition |
C42606
|
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 edition Context triple: [Quintuplex Psalterium, instanceOf, biblical edition]
-
A.
biblical text edition
chosen
A biblical text edition is a curated version of the Bible that presents a specific text form, often with scholarly annotations, critical apparatus, translations, and editorial decisions to support study, interpretation, or liturgical use.
-
B.
Jewish biblical edition
A Jewish biblical edition is a published version of the Hebrew Bible (Tanakh) that reflects Jewish textual traditions, often including the Masoretic text, traditional cantillation marks, commentaries, and sometimes translations aligned with Jewish interpretation.
-
C.
scripture library
A scripture library is a curated collection of sacred texts and related religious writings, organized for study, reference, and spiritual reflection.
-
D.
critical edition of the Hebrew Bible
A critical edition of the Hebrew Bible is a scholarly reconstruction of the biblical text that compares and evaluates all major manuscripts and textual witnesses to present the most reliable form of the original writings, accompanied by an apparatus documenting significant variants.
-
E.
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.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:11 p.m.