Triple
T30875918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omni |
E786475
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | book in the Book of Mormon |
C59098
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: book in the Book of Mormon Context triple: [Omni, instanceOf, book in the Book of Mormon]
-
A.
Book of Mormon book
chosen
A Book of Mormon book is a major subdivision of the Book of Mormon text, typically authored or named after a prophet or leader, that contains a distinct narrative or collection of teachings within the overall scripture.
-
B.
Book of Mormon figure
A Book of Mormon figure is a person or character mentioned in the Book of Mormon narrative, often playing a role in its religious, historical, or moral teachings.
-
C.
figure in Latter-day Saint scripture
A figure in Latter-day Saint scripture is an individual, divine being, or symbolic personage who appears in or is referenced by the standard works of The Church of Jesus Christ of Latter-day Saints (the Bible, Book of Mormon, Doctrine and Covenants, and Pearl of Great Price), contributing to its narrative, doctrine, or theology.
-
D.
Book of Mormon people
A group of ancient civilizations and peoples described in the Book of Mormon, including the Nephites, Lamanites, Jaredites, and others, whose histories, migrations, wars, and religious experiences are central to the narrative.
-
E.
Book of Mormon city
A Book of Mormon city is a named urban settlement referenced in the Book of Mormon narrative, characterized by its geographic setting, sociopolitical role, and involvement in religious and military events.
- F. None of above.
Provenance (1 batch)
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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:48 p.m.