Triple
T1302854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arba’ah Turim |
E27805
|
entity |
| Predicate | OrachChayimCovers |
P26793
|
FINISHED |
| Object | daily prayers and blessings |
—
|
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: daily prayers and blessings | Statement: [Arba’ah Turim, OrachChayimCovers, daily prayers and blessings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OrachChayimCovers Context triple: [Arba’ah Turim, OrachChayimCovers, daily prayers and blessings]
-
A.
includesMegillot
Indicates that one entity contains or encompasses the set of texts or items referred to as Megillot.
-
B.
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).
-
C.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
D.
subsectionOfTanakh
Indicates that one text division is a recognized subsection within the larger structure of the Tanakh.
-
E.
hasChoir
Indicates that an entity possesses, maintains, or is associated with a choir.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c115ba64819081c55fa6807e19ef |
completed | March 1, 2026, 10:43 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:51 p.m.