Triple
T10877587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | חול המועד |
E256838
|
entity |
| Predicate | דיני תפילה בו |
P72195
|
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.
halachicSection
chosen
Indicates a relationship where a subject is classified under, or associated with, a specific section or subdivision within halachic (Jewish legal) texts or rulings.
-
B.
ordinationAsRabbi
Indicates that an individual has been formally ordained and recognized with the religious status and authority of a rabbi.
-
C.
positionInAmidah
Indicates the specific location or order of a given element within the sequence of prayers that make up the Amidah.
-
D.
halachicCategory
Indicates the classification of something according to Jewish legal (halachic) categories or rulings.
-
E.
roleInHalacha
Indicates the specific function, status, or authority an entity holds within the framework of Jewish law (halacha).
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751ad8cdc819093eafaf12fc23b15 |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.