Triple

T12222188
Position Surface form Disambiguated ID Type / Status
Subject Kearny County, Kansas E291244 entity
Predicate ISOCode P208 FINISHED
Object US-KS E30311 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: US-KS | Statement: [Kearny County, Kansas, ISOCode, US-KS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: US-KS
Context triple: [Kearny County, Kansas, ISOCode, US-KS]
  • A. Kansas chosen
    Kansas is a largely rural, landlocked U.S. state known for its extensive plains, agricultural production, and central location within the country.
  • B. Kansa
    Kansa is another name for the Kaw Nation, a Native American tribe originally from the central Midwestern region of the United States, particularly present-day Kansas.
  • C. US-MT
    US-MT is the ISO 3166-2 subdivision code that uniquely identifies the U.S. state of Montana.
  • D. Kansas, Alabama
    Kansas, Alabama is a small unincorporated rural community located in Walker County in the U.S. state of Alabama.
  • E. Kansas, Georgia
    Kansas, Georgia is a small unincorporated rural community located in Carroll County in the western part of the state.
  • 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_69d6ab668acc8190963ba424049d6aee completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91c961d648190ad6ce5f7d228eee4 completed April 10, 2026, 3:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f60aa6d3d481909852a6f2f90d7a41 completed May 2, 2026, 2:31 p.m.
Created at: April 8, 2026, 9:51 p.m.