Triple
T32922706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far West temple site |
E842186
|
entity |
| Predicate | dedicatedAsTempleSiteBy |
P117342
|
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, dedicatedAsTempleSiteBy, Joseph Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedAsTempleSiteBy Context triple: [Far West temple site, dedicatedAsTempleSiteBy, Joseph Smith]
-
A.
hadTempleDedicatedTo
Indicates that a temple was formally dedicated in honor of, or for the worship of, a particular entity.
-
B.
templeDedicatedBy
chosen
Indicates that a temple was formally dedicated, consecrated, or established by a specific person, group, or authority.
-
C.
plannedTempleDedicatedBy
Indicates that a temple, while still in the planning or unbuilt stage, is intended or designated to be dedicated by a specific agent or entity.
-
D.
religiousBuildingDedicatedTo
Indicates that a religious building is formally dedicated or consecrated to a particular deity, figure, or religious concept.
-
E.
isVotiveMonumentOf
Indicates that an object is a votive monument dedicated or offered in honor of a particular entity.
- 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.