Triple
T6167055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardston Alberta Temple |
E137592
|
entity |
| Predicate | isHistoricLDSTemple |
P69169
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cardston Alberta Temple, isHistoricLDSTemple, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricLDSTemple Context triple: [Cardston Alberta Temple, isHistoricLDSTemple, true]
-
A.
hasHistoricTemple
Indicates that an entity possesses, contains, or is associated with a temple of historical significance.
-
B.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
C.
isHistoricPlace
Indicates that a place holds recognized historical significance, often due to its age, events, or cultural importance.
-
D.
hadTempleDedicatedTo
Indicates that a temple was formally dedicated in honor of, or for the worship of, a particular entity.
-
E.
hasTemplePurpose
Indicates that something (such as a building, site, or structure) is intended, used, or designated for temple-related purposes or functions.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d6366948190b35ef44dd9d6fcd6 |
completed | March 22, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:17 p.m.