Triple
T29725271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ספר דברים |
E752161
|
entity |
| Predicate | מיקום מסורתי בקריאה |
P58436
|
FINISHED |
| Object | נקרא בשבתות במחזור הקריאה השנתי |
—
|
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: נקרא בשבתות במחזור הקריאה השנתי | Statement: [ספר דברים, מיקום מסורתי בקריאה, נקרא בשבתות במחזור הקריאה השנתי]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: מיקום מסורתי בקריאה Context triple: [ספר דברים, מיקום מסורתי בקריאה, נקרא בשבתות במחזור הקריאה השנתי]
-
A.
readingLocation
chosen
Indicates the place or position where a reading activity occurs or is associated with an entity.
-
B.
readingPlacement
Indicates a relationship where an entity is assigned or located at a specific position or level based on its reading or reading-related criteria.
-
C.
readingOf
Indicates that one entity is an interpretation, measurement, or recorded value derived from another entity.
-
D.
readingOrganizer
Indicates that an entity is responsible for planning, managing, or coordinating reading-related activities or materials for others.
-
E.
readingAid
Indicates that one entity assists or facilitates another entity’s ability to read or engage in reading activities.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672ff16a08190b8840351bef56f55 |
completed | May 2, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:38 p.m.