Triple
T32921391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Lehi abridgment |
E842152
|
entity |
| Predicate | lostDateApproximate |
P877
|
FINISHED |
| Object | 1828 |
—
|
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: 1828 | Statement: [Book of Lehi abridgment, lostDateApproximate, 1828]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostDateApproximate Context triple: [Book of Lehi abridgment, lostDateApproximate, 1828]
-
A.
lostFunctionDate
Indicates the date on which a function, capability, or operational role ceased to be active or usable.
-
B.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
dateOfLoss
Indicates the specific date on which a loss event (such as damage, theft, or other covered incident) occurred.
-
D.
decayDate
Indicates the date on which something ceases to be valid, effective, or usable (i.e., when it expires or decays).
-
E.
recoveryDate
Indicates the date on which a recovery process or restoration of a prior state is completed or officially recorded.
- 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_69f6d0d6bee48190a50f31472b3e1006 |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:19 a.m.