Triple
T780958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tisha B'Av |
E16493
|
entity |
| Predicate | prohibitionsBegin |
P6166
|
FINISHED |
| Object | sunset on the eve of 9 Av |
—
|
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: sunset on the eve of 9 Av | Statement: [Tisha B'Av, prohibitionsBegin, sunset on the eve of 9 Av]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prohibitionsBegin Context triple: [Tisha B'Av, prohibitionsBegin, sunset on the eve of 9 Av]
-
A.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
B.
notableRestriction
Indicates that there is a significant limitation, constraint, or prohibition that meaningfully affects the entity or its use.
-
C.
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.
-
D.
formerLegalRestriction
Indicates that a legal restriction once applied to an entity or relationship but is no longer in effect.
-
E.
workProhibited
Indicates that an entity is not allowed or is forbidden to perform a particular work or job activity.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a90365648190ace53b0f0e87aa68 |
completed | March 1, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69a4a50bd23081908908235b8ec9201e |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.