Triple
T3719629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priestly code |
E81608
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | priestly law collection |
C5560
|
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: priestly law collection Context triple: [Priestly code, instanceOf, priestly law collection]
-
A.
ancient Near Eastern law collection
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Nasi of the Sanhedrin
The Nasi of the Sanhedrin was the president and highest-ranking official of the ancient Jewish high court, responsible for leading its deliberations, representing the Jewish people to external authorities, and guiding religious and legal policy.
-
E.
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.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:34 p.m.