Triple
T32922701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far West temple site |
E842186
|
entity |
| Predicate | cornerstonesLaidBy |
P8956
|
FINISHED |
| Object | Joseph Smith |
—
|
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: Joseph Smith | Statement: [Far West temple site, cornerstonesLaidBy, Joseph Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cornerstonesLaidBy Context triple: [Far West temple site, cornerstonesLaidBy, Joseph Smith]
-
A.
cornerstoneLaidBy
chosen
Indicates that the act of laying a building’s cornerstone was performed by a specified agent or entity.
-
B.
foundationStoneLaid
Indicates that the initial, symbolic stone marking the start of constructing a building or structure has been formally placed.
-
C.
cornerstoneLayingDate
Indicates the date on which the cornerstone of a structure or building was formally laid.
-
D.
datePlannedTempleCornerstonesLaid
Indicates the planned date on which the temple’s cornerstones are scheduled to be laid.
-
E.
providedFoundationFor
Indicates that one entity served as the essential basis, support, or groundwork enabling the existence, development, or success of another entity or outcome.
- 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_69f6d0d7b7888190b93fe5556a28c470 |
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:20 a.m.