Triple
T35468748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rexburg Idaho Temple |
E1025150
|
entity |
| Predicate | isOperatingTemple |
P100759
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rexburg Idaho Temple, isOperatingTemple, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOperatingTemple Context triple: [Rexburg Idaho Temple, isOperatingTemple, yes]
-
A.
isActiveTemple
chosen
Indicates that a temple is currently functioning and in regular religious use, rather than being abandoned, ruined, or inactive.
-
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.
templeUse
Indicates that something is used as, functions as, or serves the purpose of a temple.
-
D.
hasTempleFeature
Indicates that an entity possesses a specific architectural or structural feature characteristic of a temple.
-
E.
templeState
Indicates that a temple is in a particular condition, status, or phase (such as operational, under construction, abandoned, or ceremonial).
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.