Triple

T855997
Position Surface form Disambiguated ID Type / Status
Subject Nebraska E18492 entity
Predicate hasCity P316 FINISHED
Object Bellevue, Nebraska E57376 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: Bellevue, Nebraska | Statement: [Nebraska, hasCity, Bellevue, Nebraska]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bellevue, Nebraska
Context triple: [Nebraska, hasCity, Bellevue, Nebraska]
  • A. Bellevue, Nebraska chosen
    Bellevue, Nebraska is a historic suburb of Omaha and one of the oldest cities in the state, known for its proximity to Offutt Air Force Base and its role in the greater Omaha metropolitan area.
  • B. Jackson, Nebraska
    Jackson, Nebraska is a small rural village located in northeastern Nebraska within the Sioux City metropolitan area.
  • C. La Vista, Nebraska
    La Vista, Nebraska is a suburban city in Sarpy County that forms part of the greater Omaha metropolitan area.
  • D. Hubbard, Nebraska
    Hubbard, Nebraska is a small rural village located in northeastern Nebraska within the Sioux City metropolitan area.
  • E. North Platte, Nebraska
    North Platte, Nebraska is a small city in western Nebraska known as a major rail transportation center and home to one of the world’s largest railroad classification yards.
  • 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_69a4938bdd3c8190a954a3c11844d9cf completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac3c172481908ed164ee1579ec28 completed March 1, 2026, 9:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac939b0fbc8190a205a5033568ba9c completed March 7, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:39 p.m.