Triple

T11485343
Position Surface form Disambiguated ID Type / Status
Subject Sedgwick County, Kansas E272259 entity
Predicate contains P35 FINISHED
Object Sedgwick, Kansas E821071 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: Sedgwick, Kansas | Statement: [Sedgwick County, Kansas, contains, Sedgwick, Kansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sedgwick, Kansas
Context triple: [Sedgwick County, Kansas, contains, Sedgwick, Kansas]
  • A. Sedgwick, Kansas chosen
    Sedgwick, Kansas is a small city in south-central Kansas known for its rural community character and proximity to the Wichita metropolitan area.
  • B. Seneca, Kansas
    Seneca, Kansas is a small city in northeastern Kansas that serves as a local commercial and community hub for the surrounding rural region.
  • C. Seward, Kansas
    Seward, Kansas is a small unincorporated rural community located in Stafford County in central Kansas.
  • D. Wilson, Kansas
    Wilson, Kansas is a small rural city in central Kansas known for its Czech heritage and location near Wilson Lake.
  • E. Watson, Kansas
    Watson, Kansas is a small unincorporated rural community located in Shawnee County in the U.S. state of Kansas.
  • 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_69d6aae1b09881909ce2ded3fa0c14fa completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85a1ea00c8190b42cdc13a6bc61c3 completed April 10, 2026, 2:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69f63ed82a548190ab9326daef78e30b completed May 2, 2026, 6:13 p.m.
Created at: April 8, 2026, 9:36 p.m.