Triple

T6252288
Position Surface form Disambiguated ID Type / Status
Subject Finney County, Kansas E140074 entity
Predicate contains P35 FINISHED
Object Holcomb, Kansas E249400 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: Holcomb, Kansas | Statement: [Finney County, Kansas, contains, Holcomb, Kansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Holcomb, Kansas
Context triple: [Finney County, Kansas, contains, Holcomb, Kansas]
  • A. Holcomb, Kansas chosen
    Holcomb, Kansas is a small rural village in western Kansas best known as the real-life setting of Truman Capote’s true-crime book "In Cold Blood."
  • B. 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.
  • C. McCune, Kansas
    McCune, Kansas is a small rural city located in southeastern Kansas within the Pittsburg micropolitan area.
  • D. Altamont, Kansas
    Altamont, Kansas is a small rural city in Labette County known for its agricultural surroundings and location in the southeastern part of the state.
  • E. De Soto, Kansas
    De Soto, Kansas is a small city in northeastern Kansas that forms part of the Kansas City 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_69c008b4858c819095b0199114a9a87b completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c063417c8c8190945049881819d307 completed March 22, 2026, 9:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69c787f5123c8190957161b7afae67dd completed March 28, 2026, 7:49 a.m.
Created at: March 22, 2026, 4:24 p.m.