Triple
T16948454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deuteronomy 33:12 |
E411123
|
entity |
| Predicate | positionInChapter |
P112272
|
FINISHED |
| Object | within the Blessing of Moses |
—
|
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: within the Blessing of Moses | Statement: [Deuteronomy 33:12, positionInChapter, within the Blessing of Moses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInChapter Context triple: [Deuteronomy 33:12, positionInChapter, within the Blessing of Moses]
-
A.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
B.
rankWithinChapter
chosen
Indicates the relative ordering or position of an item among other items within the same chapter.
-
C.
foundInChapter
Indicates that something (such as a concept, section, or element) is contained within or occurs in a specific chapter.
-
D.
positionInPage
Indicates the specific location or placement of an element within a page’s layout or structure.
-
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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb4b1b08190b608d36a209ed6bd |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.