Triple

T22351529
Position Surface form Disambiguated ID Type / Status
Subject Boulder Highway E552540 entity
Predicate namedAfter P63 FINISHED
Object Boulder City NE NERFINISHED

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: Boulder City | Statement: [Boulder Highway, namedAfter, Boulder City]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Boulder City
Context triple: [Boulder Highway, namedAfter, Boulder City]
  • A. Boulder City, Nevada chosen
    Boulder City, Nevada is a planned community in southern Nevada best known for housing workers during the construction of Hoover Dam and for being one of the few U.S. cities where gambling is prohibited.
  • B. Wellington, Nevada
    Wellington, Nevada is a small unincorporated rural community in western Nevada known for ranching, agriculture, and its scenic location near the Sierra Nevada foothills.
  • C. Columbus, Nevada
    Columbus, Nevada is an abandoned 19th-century mining settlement in Esmeralda County that is now considered a ghost town.
  • D. Springfield, Nevada
    Springfield, Nevada is a small, lesser-known community in the U.S. state of Nevada.
  • E. Elko
    Elko is a small city in northeastern Nevada known as a regional hub for ranching, mining, and outdoor recreation.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e4a0ad08190a385b4d343cf6524 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1579be6d8819088fed70f54ff4e66 completed April 29, 2026, 12:58 a.m.
Created at: April 16, 2026, 8:44 p.m.