Triple
T6173650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ma’ariv |
E137763
|
entity |
| Predicate | requiresMinyanFor |
P51522
|
FINISHED |
| Object | devarim shebikdusha such as Kaddish and Barchu |
—
|
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: devarim shebikdusha such as Kaddish and Barchu | Statement: [Ma’ariv, requiresMinyanFor, devarim shebikdusha such as Kaddish and Barchu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresMinyanFor Context triple: [Ma’ariv, requiresMinyanFor, devarim shebikdusha such as Kaddish and Barchu]
-
A.
requiresMinyan
chosen
Indicates that the action or ritual can only be properly performed when a quorum (minyan) of participants is present.
-
B.
requiresZimunWhen
Indicates that a situation or context obligates the performance of Zimun (the formal invitation to communal grace after meals).
-
C.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
D.
hasFullSetOfPurimMitzvot
Indicates that an entity fulfills or possesses the complete set of religious commandments associated with the observance of Purim.
-
E.
requiresPermitFor
Indicates that one entity must obtain formal permission or authorization before performing an action involving another entity.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d94c47481909745b2533926a1ca |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.