Triple
T32922707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far West temple site |
E842186
|
entity |
| Predicate | plannedTempleName |
P151576
|
FINISHED |
| Object | Far West Temple |
—
|
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: Far West Temple | Statement: [Far West temple site, plannedTempleName, Far West Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedTempleName Context triple: [Far West temple site, plannedTempleName, Far West Temple]
-
A.
templeName
Indicates that an entity is identified by or associated with the name of a temple.
-
B.
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.
-
C.
templeTitleOf
Indicates that one entity is the formal religious or ceremonial title held by another entity within a temple or sacred context.
-
D.
isNumberedTempleOf
Indicates that one entity is a specific, designated temple identified by a particular number within a series or system associated with another entity.
-
E.
plannedName
chosen
Indicates that an entity has a proposed or intended name that is planned to be assigned to it in the future.
- 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_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 1, 2026, 1:20 a.m.