Triple
T5296837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Lake Temple |
E119875
|
entity |
| Predicate | publicOpenHouse |
P18212
|
FINISHED |
| Object | held prior to original 1893 dedication |
—
|
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: held prior to original 1893 dedication | Statement: [Salt Lake Temple, publicOpenHouse, held prior to original 1893 dedication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicOpenHouse Context triple: [Salt Lake Temple, publicOpenHouse, held prior to original 1893 dedication]
-
A.
homeVenueOpened
Indicates that a venue has officially begun operating as the designated home location for a particular team or organization.
-
B.
openedForPublic
chosen
Indicates that something has been made accessible or available for use, entry, or participation by the general public.
-
C.
homeManager
Indicates that one entity manages, oversees, or is responsible for the operations or affairs of another entity’s home or household.
-
D.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
-
E.
housesCollection
Indicates that one entity serves as a container or repository that holds or stores a collection of other entities.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.