Triple

T16888608
Position Surface form Disambiguated ID Type / Status
Subject Draper Town Center station E421604 entity
Predicate locatedIn P40 FINISHED
Object Draper, Utah E243582 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: Draper, Utah | Statement: [Draper Town Center station, locatedIn, Draper, Utah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Draper, Utah
Context triple: [Draper Town Center station, locatedIn, Draper, Utah]
  • A. Draper, Utah chosen
    Draper, Utah is a rapidly growing suburban city in the southern Salt Lake Valley known for its residential communities, tech industry presence, and access to outdoor recreation along the Wasatch Range.
  • B. Lindon, Utah
    Lindon, Utah is a small suburban city in Utah County situated along the Wasatch Front between Orem and Pleasant Grove.
  • C. Ogden, Utah
    Ogden, Utah is a city in northern Utah known as a historic railroad hub and gateway to nearby ski resorts and outdoor recreation in the Wasatch Mountains.
  • D. Woods Cross, Utah
    Woods Cross, Utah is a small suburban city in Davis County that forms part of the greater Salt Lake City metropolitan area along the Wasatch Front.
  • E. Richfield, Utah
    Richfield, Utah is a small city that serves as a regional commercial and service hub for 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_69d889d470fc8190b4aec199636c0c56 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e3bbc2f6d081909c76fa2a6b87e083 completed April 18, 2026, 5:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c2befaa88190ba83dc17aa66b541 completed May 10, 2026, 5:39 p.m.
Created at: April 10, 2026, 5:29 a.m.