Triple

T10859241
Position Surface form Disambiguated ID Type / Status
Subject American Fork, Utah E256352 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: [American Fork, Utah, locatedNear, Lehi, Utah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lehi, Utah
Context triple: [American Fork, Utah, 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_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_69e6849dbff08190a352eaaea8606bdb completed April 20, 2026, 7:55 p.m.
Created at: April 8, 2026, 9:20 p.m.