Triple
T968151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shema Yisrael |
E20882
|
entity |
| Predicate | associatedMitzvah |
P21326
|
FINISHED |
| Object | recitation twice daily |
—
|
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: recitation twice daily | Statement: [Shema Yisrael, associatedMitzvah, recitation twice daily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMitzvah Context triple: [Shema Yisrael, associatedMitzvah, recitation twice daily]
-
A.
associatedDevotion
chosen
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
B.
associatedPrayer
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
C.
roleInJudaism
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
-
D.
associatedCharity
Indicates that one entity has a formal or recognized charitable affiliation or partnership with another entity.
-
E.
associatedWithChurch
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b43549008190a4d65efdc3bda520 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a579888190afb489ac9fe8391c |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.