Triple
T24542729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Holiness |
E607139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of a halakhic code |
C17235
|
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 a halakhic code Context triple: [Book of Holiness, instanceOf, section of a halakhic code]
-
A.
part of Mishneh Torah
A part of Mishneh Torah is a distinct legal section within Maimonides’ comprehensive codification of Jewish law, addressing a specific thematic area of halakhic practice or belief.
-
B.
section of a religious text
chosen
A section of a religious text is a distinct, thematically or structurally defined subdivision—such as a chapter, verse group, or discourse unit—within a sacred scripture that conveys a coherent portion of its teachings or narrative.
-
C.
compilation of oral law
A compilation of oral law is an organized written collection of previously unwritten legal traditions, interpretations, and rulings that were transmitted orally within a community or religious-legal system.
-
D.
commentary on Shulchan Aruch
A commentary on the Shulchan Aruch is a scholarly work that explains, analyzes, and clarifies the legal rulings of this foundational Jewish code of law, often reconciling sources and applying them to practical halachic questions.
-
E.
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.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:26 a.m.