Triple
T32921383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Lehi abridgment |
E842152
|
entity |
| Predicate | coversEventsAlsoToldIn |
P58905
|
FINISHED |
| Object | 1 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: 1 Nephi | Statement: [Book of Lehi abridgment, coversEventsAlsoToldIn, 1 Nephi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversEventsAlsoToldIn Context triple: [Book of Lehi abridgment, coversEventsAlsoToldIn, 1 Nephi]
-
A.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
B.
basedOnEventsDescribedIn
Indicates that something is derived from, inspired by, or constructed using the events described in another source.
-
C.
includesEvents
chosen
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
D.
notableCoverEvent
Indicates that an entity has been the subject of a particularly significant or noteworthy cover version, performance, or reinterpretation by another entity.
-
E.
notableEventCoverage
Indicates that there is media or documented coverage specifically focused on a notable event related to the subject.
- 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_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:19 a.m.