Triple
T6422250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosh Chodesh |
E127971
|
entity |
| Predicate | hasTorahReading |
P5456
|
FINISHED |
| Object | Numbers 28:1–15 |
—
|
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: Numbers 28:1–15 | Statement: [Rosh Chodesh, hasTorahReading, Numbers 28:1–15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTorahReading Context triple: [Rosh Chodesh, hasTorahReading, Numbers 28:1–15]
-
A.
hasPublicTorahReading
Indicates that a religious event or occasion includes a formal, communal reading of the Torah in public.
-
B.
hasLiturgicalReading
chosen
Indicates that a religious service, observance, or liturgical event includes or is associated with a specific prescribed reading from scripture or other sacred text.
-
C.
containsParshiyot
Indicates that one textual or structural unit (such as a Torah scroll or section) includes within it one or more parshiyot (distinct Torah portions or sections).
-
D.
includesMegillot
Indicates that one entity contains or encompasses the set of texts or items referred to as Megillot.
-
E.
isMaterLectionis
Indicates that a letter functions as a mater lectionis, i.e., it represents a vowel sound rather than serving as a consonant.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0690576c48190b5db5464eacc9de3 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.