Triple
T30740877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | large plates of Nephi |
E782685
|
entity |
| Predicate | finalCustodian |
P114319
|
FINISHED |
| Object | Mormon |
—
|
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: Mormon | Statement: [large plates of Nephi, finalCustodian, Mormon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalCustodian Context triple: [large plates of Nephi, finalCustodian, Mormon]
-
A.
finalCessionBy
Indicates that one party makes the last or conclusive transfer or assignment of rights, claims, or property to another party.
-
B.
finalDisposition
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
-
C.
finalRealization
Indicates the culminating recognition or understanding that occurs at the end of a process, event, or sequence of actions.
-
D.
traditionalCustodianOf
chosen
Indicates that an entity holds recognized traditional responsibility, authority, or guardianship over another entity, often in a cultural, ancestral, or customary context.
-
E.
finalHomeOf
Indicates that a location is the last or ultimate home, residence, or resting place of an entity.
- 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_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 29, 2026, 8:38 p.m.