Triple
T22361733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish liturgy |
E552794
|
entity |
| Predicate | includesBlessingType |
P46638
|
FINISHED |
| Object | berakhot |
—
|
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: berakhot | Statement: [Jewish liturgy, includesBlessingType, berakhot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBlessingType Context triple: [Jewish liturgy, includesBlessingType, berakhot]
-
A.
associatedWithBlessing
chosen
Indicates a relationship in which an entity is connected to, linked with, or characterized by a blessing or act of blessing.
-
B.
blessedWith
Indicates that one entity has received a positive gift, talent, quality, or advantage attributed to another source.
-
C.
blessedBy
Indicates that one entity has conferred a blessing, favor, or sacred endorsement upon another entity.
-
D.
hasHolinessType
Indicates a relationship where an entity is assigned or associated with a specific type or category of holiness.
-
E.
containsPrayerType
Indicates that one entity includes or encompasses a specific type or category of prayer.
- 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.