Triple
T4198242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fast of Gedaliah |
E86003
|
entity |
| Predicate | haftarahReading |
P47663
|
FINISHED |
| Object | Isaiah 55:6–56:8 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: Isaiah 55:6–56:8 in many rites | Statement: [Fast of Gedaliah, haftarahReading, Isaiah 55:6–56:8 in many rites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haftarahReading Context triple: [Fast of Gedaliah, haftarahReading, Isaiah 55:6–56:8 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.
hasPublicTorahReading
Indicates that a religious event or occasion includes a formal, communal reading of the Torah in public.
-
D.
halakhicSource
Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
-
E.
includesMegillot
Indicates that one entity contains or encompasses the set of texts or items referred to as Megillot.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0360bc8081908ceb2483eef89174 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:48 p.m.