Triple
T4788936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabbat Zachor |
E106552
|
entity |
| Predicate | readingPlacement |
P58437
|
FINISHED |
| Object | maftir aliyah |
—
|
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: maftir aliyah | Statement: [Shabbat Zachor, readingPlacement, maftir aliyah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readingPlacement Context triple: [Shabbat Zachor, readingPlacement, maftir aliyah]
-
A.
readingFeature
Indicates that an entity possesses a characteristic, capability, or attribute specifically related to reading.
-
B.
readingAid
Indicates that one entity assists or facilitates another entity’s ability to read or engage in reading activities.
-
C.
readingApproach
Indicates the method, strategy, or manner in which an entity engages in reading a text.
-
D.
readingExperience
Indicates the relationship in which an entity engages with written or visual material, capturing the act, manner, or quality of that reading activity.
-
E.
containsReading
Indicates that one entity includes or encompasses a particular reading (such as a measurement, value, or interpretation) within it.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:22 p.m.