Triple

T7948788
Position Surface form Disambiguated ID Type / Status
Subject Central Utah E184560 entity
Predicate contains P35 FINISHED
Object Nephi, Utah E546275 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: Nephi, Utah | Statement: [Central Utah, contains, Nephi, Utah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nephi, Utah
Context triple: [Central Utah, contains, Nephi, Utah]
  • A. Nephi, Utah chosen
    Nephi, Utah is a small city in central Utah known as a regional agricultural and transportation hub near the Wasatch Front.
  • B. Moroni, Utah
    Moroni, Utah is a small rural city in central Utah known for its agricultural community and location within the Sanpete Valley.
  • C. Lehi, Utah
    Lehi, Utah is a rapidly growing city in northern Utah known as a major tech and business hub within the Silicon Slopes region.
  • D. 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.
  • E. 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.
  • 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_69ca8291c2008190b1b8832c87814bcf completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3b2bf6f48190ac7491c41045cab2 completed March 31, 2026, 3:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd672cb3288190af4f951e65e8d67e completed April 1, 2026, 6:42 p.m.
Created at: March 30, 2026, 5:10 p.m.