Triple

T15685853
Position Surface form Disambiguated ID Type / Status
Subject Chariton County Courthouse E380197 entity
Predicate city P40 FINISHED
Object Keytesville E1171680 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: Keytesville | Statement: [Chariton County Courthouse, city, Keytesville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Keytesville
Context triple: [Chariton County Courthouse, city, Keytesville]
  • A. Keytesville chosen
    Keytesville is a small town in Missouri that serves as the county seat of Chariton County and reflects a rural Midwestern community character.
  • B. Stewarttown
    Stewarttown is a small community located within the town of Halton Hills in Ontario, Canada.
  • C. Yatesville
    Yatesville is a small town located in the U.S. state of Georgia.
  • D. McKownville
    McKownville is a hamlet and suburban community within the town of Guilderland in Albany County, New York, known for its proximity to the city of Albany and the University at Albany campus.
  • E. Petersville
    Petersville is a small, remote community in Alaska known as a gateway to outdoor recreation and backcountry areas within the Matanuska-Susitna Borough.
  • 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_69d86d99e860819094b6957cde470f2c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e04f4b73d881908ec0f21393a01969 completed April 16, 2026, 2:54 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff756ffcc88190a72440c7b40711ff completed May 9, 2026, 5:57 p.m.
Created at: April 10, 2026, 4:44 a.m.