Triple
T22361912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahavah Rabbah |
E552797
|
entity |
| Predicate | liturgicalUnitOf |
P88147
|
FINISHED |
| Object | daily prayer |
—
|
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: daily prayer | Statement: [Ahavah Rabbah, liturgicalUnitOf, daily prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalUnitOf Context triple: [Ahavah Rabbah, liturgicalUnitOf, daily prayer]
-
A.
isPartOfLiturgicalUnit
chosen
Indicates that one element belongs to, and functions as a component within, a larger liturgical unit or structure.
-
B.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
-
C.
liturgicalFormIncludes
Indicates that one liturgical form contains, incorporates, or makes use of another liturgical element or structure.
-
D.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
E.
liturgicalMoment
Indicates the specific point or phase within a liturgical or religious service at which an action, prayer, or ritual occurs.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157d44a908190b16e4cfdf4591b10 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.