Triple
T32922705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far West temple site |
E842186
|
entity |
| Predicate | cornerstonesLaidDate |
P174611
|
FINISHED |
| Object | July 4, 1838 |
—
|
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: July 4, 1838 | Statement: [Far West temple site, cornerstonesLaidDate, July 4, 1838]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cornerstonesLaidDate Context triple: [Far West temple site, cornerstonesLaidDate, July 4, 1838]
-
A.
cornerstoneLayingDate
chosen
Indicates the date on which the cornerstone of a structure or building was formally laid.
-
B.
cornerstoneLaidBy
Indicates that the act of laying a building’s cornerstone was performed by a specified agent or entity.
-
C.
datePlannedTempleCornerstonesLaid
Indicates the planned date on which the temple’s cornerstones are scheduled to be laid.
-
D.
claimedConstructionDate
Indicates the date on which an entity is asserted or reported to have been constructed, according to some claim or source.
-
E.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
- 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_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:20 a.m.