Triple
T30873820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigham City Utah Temple |
E786416
|
entity |
| Predicate | hasPublicOpenHouse |
P139563
|
FINISHED |
| Object | August–September 2012 |
—
|
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: August–September 2012 | Statement: [Brigham City Utah Temple, hasPublicOpenHouse, August–September 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicOpenHouse Context triple: [Brigham City Utah Temple, hasPublicOpenHouse, August–September 2012]
-
A.
openHouseHeld
chosen
Indicates that an open house event was conducted or hosted for a particular property or location.
-
B.
hasPublicHouse
Indicates that one entity possesses, operates, or is associated with a public house (such as a bar or pub) as part of its facilities or holdings.
-
C.
hasPartOpenToPublic
Indicates that some portion or component of an entity is accessible for use or visitation by the general public.
-
D.
meetsOpenToPublic
Indicates that an entity satisfies the conditions required to be considered open and accessible to the general public.
-
E.
openHouseStartDate
Indicates the calendar date on which an open house event for a property is scheduled to begin.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 29, 2026, 8:48 p.m.