Triple
T10111274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plates of Mormon |
E218244
|
entity |
| Predicate | containsRecordOf |
P18283
|
FINISHED |
| Object | Nephite history |
—
|
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: Nephite history | Statement: [Plates of Mormon, containsRecordOf, Nephite history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRecordOf Context triple: [Plates of Mormon, containsRecordOf, Nephite history]
-
A.
hasRecordType
Indicates that an entity is associated with or classified under a specific type or category of record.
-
B.
hasEntryOn
chosen
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
C.
containsCorrespondenceWith
Indicates that one entity includes or holds correspondence (such as messages or communications) that is associated with or exchanged with another entity.
-
D.
containsAccountOf
Indicates that one entity includes, records, or holds information about another entity’s account.
-
E.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd0cf39908190bba679ace095eefc |
completed | April 2, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:03 p.m.