Triple
T4788910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabbat Zachor |
E106552
|
entity |
| Predicate | audienceEmphasis |
P17414
|
FINISHED |
| Object | men are especially obligated to hear the reading |
—
|
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: men are especially obligated to hear the reading | Statement: [Shabbat Zachor, audienceEmphasis, men are especially obligated to hear the reading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceEmphasis Context triple: [Shabbat Zachor, audienceEmphasis, men are especially obligated to hear the reading]
-
A.
audienceScale
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
-
B.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
-
C.
audienceSetting
Indicates the context or environment in which an audience is situated or addressed.
-
D.
culturalEmphasis
Indicates that a culture, group, or context places particular importance or priority on a specific value, practice, or domain.
-
E.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65db847081908f5456724a2bdc65 |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.