Triple
T3193656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pesukei DeZimra |
E66883
|
entity |
| Predicate | positionInService |
P5188
|
FINISHED |
| Object | near beginning of Shacharit |
—
|
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: near beginning of Shacharit | Statement: [Pesukei DeZimra, positionInService, near beginning of Shacharit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInService Context triple: [Pesukei DeZimra, positionInService, near beginning of Shacharit]
-
A.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
B.
positionInWork
chosen
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
-
C.
inService
Indicates that an entity is currently active, operational, or available for use in its intended role or function.
-
D.
inServiceFrom
Indicates the time or event from which an entity (such as a service, system, or asset) begins being operationally active or officially in use.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada713bf0c81908f3143f45f63a5ad |
completed | March 8, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.