Triple
T33054856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parashat Acharei Mot |
E845819
|
entity |
| Predicate | bookNumberInTorah |
P5479
|
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: [Parashat Acharei Mot, bookNumberInTorah, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookNumberInTorah Context triple: [Parashat Acharei Mot, bookNumberInTorah, 3]
-
A.
positionInTanakh
chosen
Indicates the relative location or ordering of a text or passage within the canonical structure of the Tanakh.
-
B.
numberOfBiblicalBooks
Indicates the total count of books contained in a specified version or canon of the Bible.
-
C.
subsectionOfTanakh
Indicates that one text division is a recognized subsection within the larger structure of the Tanakh.
-
D.
bookNumberInNewTestament
Indicates the numerical position a specific book occupies within the sequence of books in the New Testament.
-
E.
numberInBiblicalText
Indicates that a specific number appears within, or is referenced by, a given passage or unit of biblical text.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.