Triple
T3072458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shushan Purim |
E64054
|
entity |
| Predicate | liturgicalRestriction |
P6166
|
FINISHED |
| Object | Tachanun 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 omitted | Statement: [Shushan Purim, liturgicalRestriction, Tachanun omitted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalRestriction Context triple: [Shushan Purim, liturgicalRestriction, Tachanun omitted]
-
A.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
B.
religiousRestriction
chosen
Indicates that one entity imposes, experiences, or is subject to limitations or rules based on religious beliefs or practices in relation to another entity or context.
-
C.
aimsForLiturgicalUse
Indicates that something is intended or designed specifically for use in liturgical or formal religious worship contexts.
-
D.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
-
E.
liturgicalUseApprovedBy
Indicates that the use of a liturgical text, rite, or practice has been formally authorized or approved by a specified authority.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14c8bd881909cf1bb2649ba36db |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.