Triple
T1269603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishneh Torah |
E15679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish legal code |
C3962
|
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 legal code Context triple: [Mishneh Torah, instanceOf, Jewish legal code]
-
A.
ecclesiastical law code
An ecclesiastical law code is a systematic collection of rules and regulations issued by a religious authority to govern the doctrine, discipline, and organizational life of a church or religious community.
-
B.
compilation of oral law
chosen
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.
-
C.
ancient Near Eastern law collection
An ancient Near Eastern law collection is a compiled set of legal rules, case decisions, and royal decrees from early civilizations such as Mesopotamia, intended to articulate social norms, regulate behavior, and legitimize authority.
-
D.
rabbinic literature
Rabbinic literature is the body of Jewish religious writings produced by rabbinic sages, including the Mishnah, Talmud, Midrash, and related commentaries, that interpret and expand upon the Hebrew Bible and Jewish law.
-
E.
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.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:50 p.m.