Triple
T10166079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ביכורים |
E235206
|
entity |
| Predicate | ניתנים_ל |
P92175
|
FINISHED |
| Object | כהנים |
—
|
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: כהנים | Statement: [ביכורים, ניתנים_ל, כהנים]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ניתנים_ל Context triple: [ביכורים, ניתנים_ל, כהנים]
-
A.
aliyahTo
Indicates the action of a person immigrating to and settling in Israel, typically as a permanent move.
-
B.
halachicNote
Indicates a relationship where one entity serves as a halachic (Jewish legal) note, comment, or annotation providing legal clarification or guidance about another entity.
-
C.
doesNotRequireMinyanFor
Indicates that the associated action, ritual, or obligation can be performed without the presence of a quorum (minyan) of participants.
-
D.
conversionRequirementInIsrael
Indicates a requirement that a person undergo or meet specific conditions for religious conversion within the jurisdiction of Israel.
-
E.
EvenHaEzerScope
Indicates a relationship or action that falls within the legal or thematic scope defined by the Even HaEzer section of Jewish law (typically matters of marriage and family).
- F. None of above. chosen
Provenance (4 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6cf27481909f38839452ac0e37 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:10 p.m.