Triple

T5691459
Position Surface form Disambiguated ID Type / Status
Subject Southeast Kansas E125435 entity
Predicate contains P35 FINISHED
Object Uniontown, Kansas E544113 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: Uniontown, Kansas | Statement: [Southeast Kansas, contains, Uniontown, Kansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Uniontown, Kansas
Context triple: [Southeast Kansas, contains, Uniontown, Kansas]
  • A. Uniontown, Kansas chosen
    Uniontown, Kansas is a small rural city located in southeastern Kansas within Bourbon County.
  • B. Mapleton, Kansas
    Mapleton, Kansas is a small rural town located in Bourbon County in southeastern Kansas, United States.
  • C. Belvue, Kansas
    Belvue, Kansas is a small rural city in Pottawatomie County that functions as part of the greater Manhattan, Kansas regional community.
  • D. Alta Vista, Kansas
    Alta Vista, Kansas is a small rural city in eastern Kansas that functions as part of the broader Manhattan-area community.
  • E. White City, Kansas
    White City, Kansas is a small rural town in Morris County that forms part of the Manhattan, Kansas metropolitan area.
  • 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_69c0082bb19c8190823a4facd3cba79b completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c023e500ec8190bfda4f6a818aa5dc completed March 22, 2026, 5:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6855bd42c8190a9fbebd5176d63fd completed March 27, 2026, 1:25 p.m.
Created at: March 22, 2026, 3:44 p.m.