Triple
T14681731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tu B'Av |
E344802
|
entity |
| Predicate | prayerChange |
P16687
|
FINISHED |
| Object | Tachanun is omitted |
—
|
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: Tachanun is omitted | Statement: [Tu B'Av, prayerChange, Tachanun is omitted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prayerChange Context triple: [Tu B'Av, prayerChange, Tachanun is omitted]
-
A.
associatedPrayerChange
chosen
Indicates a change in a prayer that is linked or connected to another entity, event, or condition.
-
B.
prayerForm
Indicates the specific manner, style, or structure in which a prayer is expressed or performed.
-
C.
prayerCall
Indicates that one entity issues or performs a call to prayer directed toward others.
-
D.
associatedPrayer
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
E.
prayedDuring
Indicates that one entity performed prayer at some time within the duration of another specified event or time interval.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56a51ec8190941684fd562a7182 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.