Triple
T2652106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bnei Mikra |
E53922
|
entity |
| Predicate | viewOnOralLaw |
P8264
|
FINISHED |
| Object | non-binding |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: non-binding | Statement: [Bnei Mikra, viewOnOralLaw, non-binding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnOralLaw Context triple: [Bnei Mikra, viewOnOralLaw, non-binding]
-
A.
viewsHalakhaAs
chosen
Indicates that one entity regards or interprets Halakha (Jewish law) in a particular way, such as considering it authoritative, binding, flexible, or symbolic.
-
B.
halakhicSource
Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
-
C.
viewOnHadith
Indicates a relationship where an entity holds a particular interpretive stance, opinion, or evaluative perspective regarding a specific hadith.
-
D.
viewOnIjtihad
Indicates a stance or perspective an entity holds regarding the practice or principle of ijtihad (independent legal reasoning in Islamic jurisprudence).
-
E.
viewOnMoralLaw
Indicates a subject’s stance or interpretation regarding principles of moral law or ethical rules.
- F. None of above.
Provenance (3 batches)
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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abda0ba2208190ad87763ecbef8c3c |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd815d06481909535c02b0aba8553 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.