Triple

T10379965
Position Surface form Disambiguated ID Type / Status
Subject Roy, Utah E244611 entity
Predicate adjacentTo P224 FINISHED
Object Hooper, Utah E607082 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: Hooper, Utah | Statement: [Roy, Utah, adjacentTo, Hooper, Utah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hooper, Utah
Context triple: [Roy, Utah, adjacentTo, Hooper, Utah]
  • A. Hooper, Utah chosen
    Hooper, Utah is a small residential city in northern Utah known for its rural character and location within the Ogden metropolitan area.
  • B. Elwood, Utah
    Elwood, Utah is a small rural town located in northern Utah within the Bear River Valley.
  • C. Peoa, Utah
    Peoa, Utah is a small unincorporated rural community in northeastern Utah known for its agricultural character and scenic mountain setting.
  • D. 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.
  • E. Parowan, Utah
    Parowan, Utah is a small historic city in southwestern Utah known as the "Mother Town of Southern Utah" and serves as the county seat of Iron County.
  • 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_69d381b3e328819094b23b8edcd29b5a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e991056c8190a981f717c51f1f72 completed April 7, 2026, 11:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69e4415b7f848190a9fc8b08824f0b9b completed April 19, 2026, 2:43 a.m.
Created at: April 6, 2026, 12:03 p.m.