Triple
T32921397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Lehi abridgment |
E842152
|
entity |
| Predicate | replacedNarrativelyBy |
P139019
|
FINISHED |
| Object | small plates of Nephi |
—
|
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: small plates of Nephi | Statement: [Book of Lehi abridgment, replacedNarrativelyBy, small plates of Nephi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedNarrativelyBy Context triple: [Book of Lehi abridgment, replacedNarrativelyBy, small plates of Nephi]
-
A.
replacesInNarrative
chosen
Indicates that one narrative element takes the place of another within the structure or progression of a story.
-
B.
narrativeShift
Indicates a change in the narrative perspective, time, focus, or structure within a story or discourse.
-
C.
narrativeVariation
Indicates that one narrative differs from another in form, structure, or content while remaining related or derived.
-
D.
narratesAs
Indicates that one entity tells, recounts, or presents a story, event, or information in the manner, style, or voice of another entity.
-
E.
narratedTo
Indicates that one entity tells or recounts a story, event, or information directly to another entity as the audience.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 1, 2026, 1:19 a.m.