Triple
T29926989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bountiful Utah Temple |
E760107
|
entity |
| Predicate | publicOpenHouseStartDate |
P111000
|
FINISHED |
| Object | 1994-11-04 |
—
|
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: 1994-11-04 | Statement: [Bountiful Utah Temple, publicOpenHouseStartDate, 1994-11-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicOpenHouseStartDate Context triple: [Bountiful Utah Temple, publicOpenHouseStartDate, 1994-11-04]
-
A.
openHouseStartDate
chosen
Indicates the calendar date on which an open house event for a property is scheduled to begin.
-
B.
openHouseHeld
Indicates that an open house event was conducted or hosted for a particular property or location.
-
C.
phase1OpeningDate
Indicates the date on which the first phase of a project, development, or initiative is officially opened or begins operation.
-
D.
rerAOpeningDate
Indicates the date on which something (such as a facility, service, or route) is opened again after having been closed.
-
E.
plannedOpeningDate
Indicates the date on which something is scheduled or intended to begin operating or become available.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 29, 2026, 6:16 p.m.