Triple
T30792267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moroni |
E784127
|
entity |
| Predicate | angelicRole |
P143890
|
FINISHED |
| Object | messenger to Joseph Smith |
—
|
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: messenger to Joseph Smith | Statement: [Moroni, angelicRole, messenger to Joseph Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: angelicRole Context triple: [Moroni, angelicRole, messenger to Joseph Smith]
-
A.
angelicRank
Indicates the hierarchical rank or level an angel holds within a system of angelic orders.
-
B.
angelicHierarchy
Indicates a hierarchical relationship in which one angelic being holds a higher or lower rank or order relative to another within a structured celestial order.
-
C.
liturgicalRole
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
D.
roleInTheProphecy
Indicates that an entity holds a specific function, status, or significance within the context of a particular prophecy.
-
E.
religiousAndSpiritualRole
chosen
Indicates that an entity holds or fulfills a religious or spiritual function, office, or responsibility in relation to another entity or context.
- 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_69f6900f50ec8190be2ee3c76edc8502 |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:42 p.m.