Triple
T8146397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah Lake |
E190221
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Lehi, Utah |
E239887
|
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: Lehi, Utah | Statement: [Utah Lake, locatedNear, Lehi, Utah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lehi, Utah Context triple: [Utah Lake, locatedNear, Lehi, Utah]
-
A.
Lehi, Utah
chosen
Lehi, Utah is a rapidly growing city in northern Utah known as a major tech and business hub within the Silicon Slopes region.
-
B.
Nephi, Utah
Nephi, Utah is a small city in central Utah known as a regional agricultural and transportation hub near the Wasatch Front.
-
C.
Moroni, Utah
Moroni, Utah is a small rural city in central Utah known for its agricultural community and location within the Sanpete Valley.
-
D.
Layton, Utah
Layton, Utah is a rapidly growing suburban city along the Wasatch Front, known as a major residential and commercial hub between Salt Lake City and Ogden.
-
E.
Manti, Utah
Manti, Utah is a small historic city in central Utah best known for its prominent Latter-day Saint temple and pioneer-era architecture.
- 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4447dbc48190affb0f34f6c85f5a |
completed | March 31, 2026, 3:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfb9eaebb88190b127905f58fd5c79 |
completed | April 3, 2026, 1 p.m. |
Created at: March 30, 2026, 5:36 p.m.