Triple
T10112110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | golden plates |
E218264
|
entity |
| Predicate | claimedReturnToHeavenlyMessengerYear |
P92252
|
FINISHED |
| Object | 1829 |
—
|
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: 1829 | Statement: [golden plates, claimedReturnToHeavenlyMessengerYear, 1829]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedReturnToHeavenlyMessengerYear Context triple: [golden plates, claimedReturnToHeavenlyMessengerYear, 1829]
-
A.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
B.
returnYear
Indicates the year in which something is returned or given back to its original owner, place, or state.
-
C.
yearOfNoReturnForTribute
Indicates the specific year after which a tribute obligation is no longer expected, valid, or required to be paid.
-
D.
confirmationYear
Indicates the calendar year in which a confirmation event or formal validation of something took place.
-
E.
returnedToManagingYear
Indicates that an entity has resumed or gone back to a previously assigned managing year after a change or interruption.
- F. None of above. chosen
Provenance (4 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_69cdd15d1fd081908c6f6b021e3999da |
completed | April 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8f869c8190a82ad040993e0244 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:03 p.m.