Triple
T8980976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herriman |
E214523
|
entity |
| Predicate | isLocatedNear |
P350
|
FINISHED |
| Object | Riverton |
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 | Statement: [Herriman, isLocatedNear, Riverton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Riverton Context triple: [Herriman, isLocatedNear, Riverton]
-
A.
Riverton
Riverton is a suburban city in the southern part of the Salt Lake Valley in Utah, known for its residential communities and family-oriented amenities.
-
B.
Lewistown
Lewistown is a small village in the Ogmore Valley of south Wales, historically associated with coal mining and the broader industrial heritage of the region.
-
C.
Holladay
Holladay is a suburban city in the Salt Lake City metropolitan area in northern Utah, known for its residential neighborhoods and proximity to the Wasatch Mountains.
-
D.
Riverton, Utah
chosen
Riverton, Utah is a suburban city in Salt Lake County that forms part of the rapidly growing Wasatch Front metropolitan region.
-
E.
Herriman
Herriman is a rapidly growing suburban city located in the southwestern part of the Salt Lake City metropolitan area in Utah.
- 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_69ca839ea8b88190922c6a326ffcc0d3 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67a76f748190a4abad5d53d58fa8 |
completed | April 1, 2026, 12:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc974f0f8819085c63deb53b95b80 |
completed | April 3, 2026, 2:06 p.m. |
Created at: March 30, 2026, 7:03 p.m.