Triple
T32922726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far West temple site |
E842186
|
entity |
| Predicate | originalUseIntended |
P75472
|
FINISHED |
| Object | site for temple for worship and church governance |
—
|
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: site for temple for worship and church governance | Statement: [Far West temple site, originalUseIntended, site for temple for worship and church governance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalUseIntended Context triple: [Far West temple site, originalUseIntended, site for temple for worship and church governance]
-
A.
originalPrimaryUse
chosen
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
-
B.
originUse
Indicates that one entity is used as the original source, basis, or starting point for the creation, derivation, or use of another entity.
-
C.
originalIntendedSetting
Indicates the context, environment, or circumstances for which something was initially designed or meant to be used.
-
D.
isIntendedForUseBy
Indicates that something is designed, meant, or purposed to be used by a particular entity or group.
-
E.
originalIntendedStatus
Indicates the status that was initially planned or expected for an entity before any changes or updates occurred.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0207a1272c81909dcdb6e3307702f5 |
completed | May 11, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a0205fa1e608190829fd2baa0434fff |
completed | May 11, 2026, 4:38 p.m. |
Created at: May 1, 2026, 1:20 a.m.