Triple

T10859243
Position Surface form Disambiguated ID Type / Status
Subject American Fork, Utah E256352 entity
Predicate locatedNear P294 FINISHED
Object Highland, Utah E882682 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: Highland, Utah | Statement: [American Fork, Utah, locatedNear, Highland, Utah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Highland, Utah
Context triple: [American Fork, Utah, locatedNear, Highland, Utah]
  • A. Highland, Utah chosen
    Highland, Utah is a suburban city in northern Utah County known for its family-oriented communities, proximity to the Wasatch Mountains, and location within the fast-growing Provo–Orem metropolitan area.
  • B. Mt. Pleasant, Utah
    Mt. Pleasant, Utah is a small historic city in central Utah known for its pioneer-era architecture and rural, agricultural character.
  • C. Blanding, Utah
    Blanding, Utah is a small city in southeastern Utah that serves as a gateway community to the Bears Ears region and numerous archaeological and outdoor recreation sites on the Colorado Plateau.
  • D. Elwood, Utah
    Elwood, Utah is a small rural town located in northern Utah within the Bear River Valley.
  • E. Lynndyl, Utah
    Lynndyl, Utah is a small rural town in central Utah known for its agricultural surroundings and proximity to major rail lines.
  • 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_69d6aa83d1448190a66d93c32394d21f completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d751500e248190823a16f2c85ad829 completed April 9, 2026, 7:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69e4417f4dfc8190bd50cec0bc52a9cc completed April 19, 2026, 2:44 a.m.
Created at: April 8, 2026, 9:20 p.m.