Triple
T4788938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabbat Zachor |
E106552
|
entity |
| Predicate | commonHaftarah |
P47663
|
FINISHED |
| Object | 1 Samuel 15:2–34 in many rites |
—
|
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: 1 Samuel 15:2–34 in many rites | Statement: [Shabbat Zachor, commonHaftarah, 1 Samuel 15:2–34 in many rites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonHaftarah Context triple: [Shabbat Zachor, commonHaftarah, 1 Samuel 15:2–34 in many rites]
-
A.
Haftarah
chosen
Indicates the relationship in which a specific prophetic reading from the Nevi'im is designated to accompany a particular Torah portion or liturgical occasion.
-
B.
subsectionOfTanakh
Indicates that one text division is a recognized subsection within the larger structure of the Tanakh.
-
C.
includesMegillot
Indicates that one entity contains or encompasses the set of texts or items referred to as Megillot.
-
D.
rabbinicSource
Indicates that one entity serves as a rabbinic or Talmudic source or authority for the other.
-
E.
blessingFromMosesText
Indicates that the text expresses or contains a blessing given by Moses.
- 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.