Triple

T11175087
Position Surface form Disambiguated ID Type / Status
Subject Burgin, Kentucky E264389 entity
Predicate hasAbbreviation P43 FINISHED
Object Burgin, KY E264389 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: Burgin, KY | Statement: [Burgin, Kentucky, hasAbbreviation, Burgin, KY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burgin, KY
Context triple: [Burgin, Kentucky, hasAbbreviation, Burgin, KY]
  • A. Burgin, Kentucky chosen
    Burgin, Kentucky is a small home rule-class city located in Mercer County in the central part of the state.
  • B. Brownsville, Kentucky
    Brownsville, Kentucky is a small city that serves as the county seat of Edmonson County and a gateway to nearby Mammoth Cave National Park.
  • C. Bloomfield, Kentucky
    Bloomfield, Kentucky is a small historic city located in central Kentucky that serves as one of the communities within Nelson County.
  • D. Benton, Kentucky
    Benton, Kentucky is a small city in western Kentucky that serves as the administrative and commercial hub of Marshall County.
  • E. Guston, Kentucky
    Guston, Kentucky is an unincorporated rural community located in Meade County in the north-central part of the state.
  • 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_69d6aa9dafac8190bd90d2c74f661aa7 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e897774c819088ebc7231cebfba6 completed April 9, 2026, 5:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69e483816af08190877f86ee52846581 completed April 19, 2026, 7:25 a.m.
Created at: April 8, 2026, 9:29 p.m.