Triple
T19591806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deuteronomy 25:17–19 |
E470253
|
entity |
| Predicate | containsMitzvotCount |
P2331
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Deuteronomy 25:17–19, containsMitzvotCount, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMitzvotCount Context triple: [Deuteronomy 25:17–19, containsMitzvotCount, 3]
-
A.
consideredMitzvahIn
Indicates that an action or practice is regarded as a mitzvah (a religiously commanded or meritorious deed) within a specified context, system, or tradition.
-
B.
hasFullSetOfPurimMitzvot
Indicates that an entity fulfills or possesses the complete set of religious commandments associated with the observance of Purim.
-
C.
numberOfCommandments
chosen
Indicates the total count of commandments associated with a given subject.
-
D.
containsCommandment
Indicates that one entity includes or encompasses a specific commandment as part of its content or structure.
-
E.
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).
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6405646f0819089436d5517c03047 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.