Triple

T8837643
Position Surface form Disambiguated ID Type / Status
Subject Stafford County, Kansas E210305 entity
Predicate largestCity P235 FINISHED
Object St. John, Kansas E792290 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: St. John, Kansas | Statement: [Stafford County, Kansas, largestCity, St. John, Kansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: St. John, Kansas
Context triple: [Stafford County, Kansas, largestCity, St. John, Kansas]
  • A. St. John, Kansas chosen
    St. John, Kansas is a small city in central Kansas known for serving as the administrative and commercial hub of Stafford County.
  • B. Thayer, Kansas
    Thayer, Kansas is a small rural city located in Neosho County in southeastern Kansas, known for its agricultural surroundings and small-town community.
  • C. De Soto, Kansas
    De Soto, Kansas is a small city in northeastern Kansas that forms part of the Kansas City metropolitan area.
  • D. Kimball, Kansas
    Kimball, Kansas is a small unincorporated community located in Neosho County in southeastern Kansas.
  • E. Humboldt, Kansas
    Humboldt, Kansas is a small historic city in Allen County known for its 19th-century roots, role in the Civil War era, and location along the Neosho River in southeastern 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_69ca8388549c819095fd94eadefbb007 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc606adde08190825dbdabd199c025 completed April 1, 2026, 12:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0f35010e481909efa384a314b6a45 completed April 4, 2026, 11:17 a.m.
Created at: March 30, 2026, 6:48 p.m.