Triple
T31064320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codes of Jewish law |
E791626
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | genre of religious legal literature |
C17183
|
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: genre of religious legal literature Context triple: [Codes of Jewish law, instanceOf, genre of religious legal literature]
-
A.
religious literature
Religious literature is a body of written works—such as scriptures, theological treatises, devotional texts, and spiritual narratives—created to express, interpret, and transmit the beliefs, practices, values, and experiences of a religious tradition.
-
B.
biblical genre
A biblical genre is a category of biblical literature characterized by distinct forms, styles, and purposes (such as narrative, law, poetry, prophecy, wisdom, or epistle) that shape how its texts are interpreted.
-
C.
religious text carrier
A religious text carrier is an entity (person, object, or medium) that transports, preserves, or conveys sacred writings from one place, time, or audience to another.
-
D.
Islamic theological text
An Islamic theological text is a written work that systematically explores, explains, and defends Islamic beliefs about God, prophecy, revelation, and the unseen, often engaging with philosophical and doctrinal debates.
-
E.
religious legislation
chosen
Religious legislation is a body of laws and legal principles derived from or heavily influenced by religious doctrines, governing behavior, rights, and obligations within a society or community.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:01 p.m.