Triple

T23069491
Position Surface form Disambiguated ID Type / Status
Subject Montgomery County, Kansas E575151 entity
Predicate contains P35 FINISHED
Object Elk City, 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: Elk City, Kansas | Statement: [Montgomery County, Kansas, contains, Elk City, Kansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elk City, Kansas
Context triple: [Montgomery County, Kansas, contains, Elk City, Kansas]
  • A. Elk City, Kansas chosen
    Elk City, Kansas is a small rural town in Montgomery County in southeastern Kansas, United States.
  • B. Elk City
    Elk City is a small city in western Oklahoma known historically for its role as a stop along U.S. Route 66 and its regional oil and gas industry.
  • C. Osage City, Kansas
    Osage City, Kansas is a small city in east-central Kansas that serves as the largest community in Osage County and has historical roots in the region’s coal mining and railroad industries.
  • D. Eudora, Kansas
    Eudora, Kansas is a small city in northeastern Kansas located between Lawrence and the Kansas City metropolitan area.
  • E. Park City, Kansas
    Park City, Kansas is a small suburban city in south-central Kansas that forms part of the Wichita metropolitan area.
  • 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_69e245bd6e4c8190bb8942245b68cad5 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f189a676c08190863c034663406018 completed April 29, 2026, 4:31 a.m.
Created at: April 17, 2026, 3:55 p.m.