Triple

T15572215
Position Surface form Disambiguated ID Type / Status
Subject Caneyville, Kentucky E374272 entity
Predicate hasNearbyCity P350 FINISHED
Object Leitchfield, Kentucky E362578 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: Leitchfield, Kentucky | Statement: [Caneyville, Kentucky, hasNearbyCity, Leitchfield, Kentucky]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leitchfield, Kentucky
Context triple: [Caneyville, Kentucky, hasNearbyCity, Leitchfield, Kentucky]
  • A. Leitchfield, Kentucky chosen
    Leitchfield, Kentucky is a small city in central Kentucky that serves as the administrative and commercial hub of Grayson County.
  • B. Shively, Kentucky
    Shively, Kentucky is a home rule-class city in Jefferson County that functions as a residential suburb of Louisville.
  • C. Riverwood, Kentucky
    Riverwood, Kentucky is a small, affluent residential city in Jefferson County that forms part of the suburban Louisville area.
  • D. Scottsville, Kentucky
    Scottsville, Kentucky is a small city that serves as the county seat of Allen County and a local hub for the surrounding rural region.
  • E. Muldraugh, Kentucky
    Muldraugh, Kentucky is a small city in north-central Kentucky known for its proximity to Fort Knox and its location along U.S. Route 31W.
  • 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_69d85ccd575081908909b71a3f3e3a61 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e2025888190a2b6240296bba13e completed April 16, 2026, 2:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff82e56ffc81909e3228a660df4e09 completed May 9, 2026, 6:54 p.m.
Created at: April 10, 2026, 4:10 a.m.