Triple

T22432038
Position Surface form Disambiguated ID Type / Status
Subject Neosho Co. E554523 entity
Predicate hasCountySeat P383 FINISHED
Object Erie, Kansas 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: Erie, Kansas | Statement: [Neosho Co., hasCountySeat, Erie, Kansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Erie, Kansas
Context triple: [Neosho Co., hasCountySeat, Erie, Kansas]
  • A. Erie, Kansas chosen
    Erie, Kansas is a small rural city that serves as the county seat of Neosho County in southeastern Kansas.
  • B. Eureka, Kansas
    Eureka, Kansas is a small city in Greenwood County that serves as a local hub for the surrounding rural area in southeastern Kansas.
  • C. Ellsworth, Kansas
    Ellsworth, Kansas is a small central Kansas city historically known as a 19th-century cattle town and later as the site of institutions such as St. Joseph Military Academy.
  • D. White City, Kansas
    White City, Kansas is a small rural town in Morris County that forms part of the Manhattan, Kansas metropolitan area.
  • E. Oneida, Kansas
    Oneida, Kansas is a small rural city located in Nemaha County in the northeastern part of the state.
  • 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_69e11e5010e48190ae1e9c9db9697637 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15a32139481909baaf9275f5e0257 completed April 29, 2026, 1:09 a.m.
Created at: April 16, 2026, 8:47 p.m.