Triple
T30873802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigham City Utah Temple |
E786416
|
entity |
| Predicate | numberInChurch |
P202692
|
FINISHED |
| Object | 14th temple in Utah |
—
|
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: 14th temple in Utah | Statement: [Brigham City Utah Temple, numberInChurch, 14th temple in Utah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInChurch Context triple: [Brigham City Utah Temple, numberInChurch, 14th temple in Utah]
-
A.
hasNumberOfChurches
Indicates the relationship that specifies how many churches are associated with a given entity.
-
B.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
-
C.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
D.
withinChurch
Indicates that one entity is located inside or contained within a church.
-
E.
particularChurch
Indicates that one entity is a specific, individual church associated with or belonging to another entity (such as a denomination, region, or organization).
- F. None of above. chosen
Provenance (4 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_6a00ada2903481908b28ce55ef97a6c2 |
completed | May 10, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_6a00ad5d23788190b3f9e2de761d39bb |
completed | May 10, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_6a00ada1f3588190a7138e9f9afb9a6b |
completed | May 10, 2026, 4:09 p.m. |
Created at: April 29, 2026, 8:48 p.m.