Triple
T17306847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vezot Haberakhah |
E420185
|
entity |
| Predicate | positionInTorah |
P6325
|
FINISHED |
| Object | 54th |
—
|
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: 54th | Statement: [Vezot Haberakhah, positionInTorah, 54th]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTorah Context triple: [Vezot Haberakhah, positionInTorah, 54th]
-
A.
positionInTanakh
Indicates the relative location or ordering of a text or passage within the canonical structure of the Tanakh.
-
B.
positionInHebrewBible
chosen
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
-
C.
positionInTalmud
Indicates the specific location or ordering of a passage, topic, or element within the structured text of the Talmud.
-
D.
positionInMishnehTorah
Indicates the specific location or ordering of a given item within the structure of the Mishneh Torah text.
-
E.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4390005dc81908345ebb6dd970582 |
completed | April 19, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.