Triple

T1769820
Position Surface form Disambiguated ID Type / Status
Subject Montana E38848 entity
Predicate largestCity P235 FINISHED
Object Billings E45126 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: Billings | Statement: [Montana, largestCity, Billings]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Billings
Context triple: [Montana, largestCity, Billings]
  • A. Billings chosen
    Billings is the largest city in the U.S. state of Montana and a major economic and cultural hub for the surrounding Mountain States region.
  • B. Billings
    Billings is a small rural municipality located on Manitoulin Island in Ontario, Canada.
  • C. Missoula
    Missoula is a vibrant city in western Montana known for its university, outdoor recreation, and cultural scene.
  • D. Cheyenne
    Cheyenne is the capital and most populous city of Wyoming, known for its historic railroad roots and annual Cheyenne Frontier Days rodeo.
  • E. Cheyenne
    The Cheyenne are a Native American people of the Great Plains known for their nomadic horse culture, warrior societies, and significant role in 19th-century U.S. frontier history.
  • 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_69a8862e61708190af97b9838cc3f5de completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa648eb9488190b1be2d2b6d259634 completed March 6, 2026, 5:22 a.m.
NED1 Entity disambiguation (via context triple) batch_69adeaceae088190a5ee93e6b46360cc completed March 8, 2026, 9:31 p.m.
Created at: March 4, 2026, 7:31 p.m.