Triple
T21196642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silicon Slopes technology corridor |
E522342
|
entity |
| Predicate | statePolicyContext |
P50615
|
FINISHED |
| Object | benefits from Utah pro-business climate |
—
|
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: benefits from Utah pro-business climate | Statement: [Silicon Slopes technology corridor, statePolicyContext, benefits from Utah pro-business climate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statePolicyContext Context triple: [Silicon Slopes technology corridor, statePolicyContext, benefits from Utah pro-business climate]
-
A.
policyContext
Indicates the situational or regulatory framework within which a policy is defined, interpreted, or applied.
-
B.
statePoliticalContext
chosen
Indicates the political situation, structures, or dynamics associated with a particular state or governmental entity.
-
C.
locationPolicy
Indicates a rule or constraint governing where an entity is allowed, required, or restricted to be located.
-
D.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
E.
closurePolicyContext
Indicates the policy or set of rules that governs how and under what conditions a process, case, or entity is brought to closure.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7333bd7a0819084bbd1d6c111bc65 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:08 p.m.