Triple

T9205795
Position Surface form Disambiguated ID Type / Status
Subject Riley County, Kansas E220974 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: [Riley County, Kansas, ISOCode, US-KS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: US-KS
Context triple: [Riley 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_69ca83e9d0e081908bdb71097201a06c completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccd947a0a08190966f22a6207c9120 completed April 1, 2026, 8:37 a.m.
NED1 Entity disambiguation (via context triple) batch_69d065e09fbc81908159b386038b3d73 completed April 4, 2026, 1:14 a.m.
Created at: March 30, 2026, 7:26 p.m.