Triple
T29725209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ספר שמות |
E752160
|
entity |
| Predicate | includesParasha |
P21342
|
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: [ספר שמות, includesParasha, שמות]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesParasha Context triple: [ספר שמות, includesParasha, שמות]
-
A.
containsParshiyot
chosen
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).
-
B.
associatedWithParashah
Indicates that one entity has a specified relationship, connection, or linkage to a particular parashah (a section of biblical text).
-
C.
includesMegillot
Indicates that one entity contains or encompasses the set of texts or items referred to as Megillot.
-
D.
subsectionOfTanakh
Indicates that one text division is a recognized subsection within the larger structure of the Tanakh.
-
E.
appearsInTractate
Indicates that one entity (such as a topic, law, or passage) is contained within or discussed in a particular tractate.
- 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_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: April 28, 2026, 7:38 p.m.