Triple
T34004347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Payson Utah Temple |
E871917
|
entity |
| Predicate | servesStakeUnitsFrom |
P200185
|
FINISHED |
| Object | Utah County |
—
|
NE NERFINISHED |
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: Utah County | Statement: [Payson Utah Temple, servesStakeUnitsFrom, Utah County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesStakeUnitsFrom Context triple: [Payson Utah Temple, servesStakeUnitsFrom, Utah County]
-
A.
hasStake
Indicates that one entity holds an interest, share, or involvement—financial, strategic, or otherwise—in another entity or outcome.
-
B.
reducedStakeIn
Indicates that one entity has decreased its ownership share or investment interest in another entity compared to a previous level.
-
C.
ownershipStake
Indicates that one entity holds a partial or full ownership interest or equity stake in another entity.
-
D.
acquiredStakeIn
Indicates that one entity has obtained an ownership interest or shareholding in another entity.
-
E.
stakeDrivenBy
Indicates that the stake or interest in something is motivated, influenced, or determined by a specified driving factor or agent.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
| PDg | Predicate description generation | batch_69ff79e645c08190a974b5239efac35b |
completed | May 9, 2026, 6:16 p.m. |
Created at: May 1, 2026, 1:50 a.m.