Triple
T30741247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Ether |
E782693
|
entity |
| Predicate | positionInBookOfMormon |
P94954
|
FINISHED |
| Object | second-to-last book |
—
|
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: second-to-last book | Statement: [Book of Ether, positionInBookOfMormon, second-to-last book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInBookOfMormon Context triple: [Book of Ether, positionInBookOfMormon, second-to-last book]
-
A.
functionInBookOfMormon
Indicates that a particular function, role, or purpose is described or carried out within the text of the Book of Mormon.
-
B.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
C.
positionInScripture
chosen
Indicates the specific location or ordering of a passage, verse, or element within a scriptural text.
-
D.
positionAmongGospels
Indicates the numerical order or placement of a given gospel within the sequence of all gospels.
-
E.
positionInHebrewBible
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 29, 2026, 8:38 p.m.