Triple

T11696803
Position Surface form Disambiguated ID Type / Status
Subject Green River E278015 entity
Predicate hasCityOnBank P7935 FINISHED
Object Greensburg, Kentucky E252471 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: Greensburg, Kentucky | Statement: [Green River, hasCityOnBank, Greensburg, Kentucky]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Greensburg, Kentucky
Context triple: [Green River, hasCityOnBank, Greensburg, Kentucky]
  • A. Greensburg, Kentucky chosen
    Greensburg, Kentucky is a small historic city in central Kentucky that serves as the county seat of Green County.
  • 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. Guston, Kentucky
    Guston, Kentucky is an unincorporated rural community located in Meade County in the north-central part of the state.
  • D. Burgin, Kentucky
    Burgin, Kentucky is a small home rule-class city located in Mercer County in the central part of the state.
  • E. Millersburg, Kentucky
    Millersburg, Kentucky is a small historic town in Bourbon County that forms part of the greater Lexington–Fayette region in central Kentucky.
  • 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_69d6aafe02d881909900d54ad7d4af84 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a47cef60819088b7cc3a3a711e4c completed April 10, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69ef833084988190b5004c93f68dc628 completed April 27, 2026, 3:39 p.m.
Created at: April 8, 2026, 9:40 p.m.