Triple
T30974828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nephi |
E789201
|
entity |
| Predicate | consideredRighteousBy |
P79418
|
FINISHED |
| Object | Latter-day Saints |
—
|
NE NERFINISHED |
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: Latter-day Saints | Statement: [Nephi, consideredRighteousBy, Latter-day Saints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredRighteousBy Context triple: [Nephi, consideredRighteousBy, Latter-day Saints]
-
A.
fateOfRighteous
Indicates the ultimate outcome or destiny that befalls those who are considered righteous.
-
B.
namedByGod
Indicates that an entity has been given its name directly by God.
-
C.
isConsideredByAdherents
Indicates that something (such as a belief, practice, object, or figure) is regarded or held in a particular way by the people who adhere to a specific faith, ideology, or group.
-
D.
pietyReputation
chosen
Indicates the degree to which an entity is regarded as devout, virtuous, or religiously upright based on its perceived behavior or character.
-
E.
consideredScriptureBy
Indicates that one party regards or recognizes a text or writing as sacred scripture.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 8:55 p.m.