Triple
T6343765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiberian cantillation |
E142694
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Masoretic tradition |
C1984
|
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: Masoretic tradition Context triple: [Tiberian cantillation, instanceOf, Masoretic tradition]
-
A.
Hebrew cantillation marks
Hebrew cantillation marks are a system of symbols added to biblical texts that indicate melodic chanting patterns, syntactic breaks, and accentuation for liturgical reading.
-
B.
Jewish liturgical corpus
The Jewish liturgical corpus is the body of prayers, blessings, poems, and scriptural readings developed across Jewish history and communities for use in communal and private worship throughout the religious calendar and life-cycle events.
-
C.
Biblical manuscript tradition
chosen
The biblical manuscript tradition encompasses the historical transmission, copying, preservation, and variation of biblical texts across languages, regions, and centuries.
-
D.
Jewish interpretive technique
A Jewish interpretive technique is a systematic method used to analyze, explain, and derive meaning from Jewish texts—especially the Hebrew Bible and rabbinic literature—through established hermeneutic principles and traditions.
-
E.
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.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:31 p.m.