Triple
T5558130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sefer Zeraim |
E145698
|
entity |
| Predicate | religiousLawFor |
P6460
|
FINISHED |
| Object | Jewish people |
—
|
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: Jewish people | Statement: [Sefer Zeraim, religiousLawFor, Jewish people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousLawFor Context triple: [Sefer Zeraim, religiousLawFor, Jewish people]
-
A.
religiousJurisdiction
Indicates that one entity holds official religious authority or governance over another entity or area.
-
B.
religiousRestriction
Indicates that one entity imposes, experiences, or is subject to limitations or rules based on religious beliefs or practices in relation to another entity or context.
-
C.
halakhicSource
Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
-
D.
scripturalLawCode
chosen
Indicates that one entity is a law code or set of legal prescriptions as defined or authorized by a particular scriptural or religious text for another entity.
-
E.
religiousCanon
Indicates that something is formally recognized as part of an established body of authoritative religious texts or doctrine.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0201529a88190bf0135e032b048ea |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.