Triple
T19427498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan River Parkway |
E486020
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Riverton, Utah |
E276208
|
NE 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: Riverton, Utah | Statement: [Jordan River Parkway, passesThrough, Riverton, Utah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Riverton, Utah Context triple: [Jordan River Parkway, passesThrough, Riverton, Utah]
-
A.
Riverton, Utah
chosen
Riverton, Utah is a suburban city in Salt Lake County that forms part of the rapidly growing Wasatch Front metropolitan region.
-
B.
Richfield, Utah
Richfield, Utah is a small city that serves as a regional commercial and service hub for central Utah.
-
C.
Elwood, Utah
Elwood, Utah is a small rural town located in northern Utah within the Bear River Valley.
-
D.
Orem, Utah
Orem, Utah is a rapidly growing city along the Wasatch Front known for its family-friendly suburbs, proximity to Brigham Young University, and role as a commercial and educational hub in central Utah.
-
E.
Riverside, Utah
Riverside, Utah is a small unincorporated rural community in northern Utah known for its agricultural character and proximity to the Bear River.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6321abb9c81908ad73c2cd537d0f1 |
completed | April 20, 2026, 2:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a08e81e54d4819099def0167ac64e26 |
completed | May 16, 2026, 9:56 p.m. |
Created at: April 10, 2026, 1:37 p.m.