Triple

T8146329
Position Surface form Disambiguated ID Type / Status
Subject Utah Valley E190220 entity
Predicate contains P35 FINISHED
Object Lehi 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 | Statement: [Utah Valley, contains, Lehi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lehi
Context triple: [Utah Valley, contains, Lehi]
  • A. Lehi
    Lehi was a radical Zionist paramilitary organization in Mandatory Palestine known for its militant struggle against British rule and controversial tactics during the 1940s.
  • B. 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.
  • C. Kanosh
    Kanosh is a small town in central Utah known for its rural setting and historical ties to the early Mormon settlement of Millard County.
  • D. Moroni
    Moroni is the largest city and political, economic, and cultural center of the island nation of Comoros in the Indian Ocean.
  • E. Nephi, Utah
    Nephi, Utah is a small city in central Utah known as a regional agricultural and transportation hub near the Wasatch Front.
  • 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_69ca82be7ba8819087de0147e9292c83 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb4447dbc48190affb0f34f6c85f5a completed March 31, 2026, 3:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc94b667d88190a0b47c7e0e07f338 completed April 1, 2026, 3:44 a.m.
Created at: March 30, 2026, 5:36 p.m.