Triple
T30792246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moroni |
E784127
|
entity |
| Predicate | roleInBookOfMormon |
P86621
|
FINISHED |
| Object | lastNephiteProphet |
—
|
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: lastNephiteProphet | Statement: [Moroni, roleInBookOfMormon, lastNephiteProphet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBookOfMormon Context triple: [Moroni, roleInBookOfMormon, lastNephiteProphet]
-
A.
functionInBookOfMormon
chosen
Indicates that a particular function, role, or purpose is described or carried out within the text of the Book of Mormon.
-
B.
roleInTheProphecy
Indicates that an entity holds a specific function, status, or significance within the context of a particular prophecy.
-
C.
biblicalFigureRole
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
D.
religiousRoleInFiction
Indicates that an entity holds or performs a religious role or function within a fictional context or narrative.
-
E.
religiousTextRole
Indicates the specific role or function that a religious text has in relation to a person, group, practice, or tradition.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
Created at: April 29, 2026, 8:42 p.m.