Triple
T21343801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clinton County, Kentucky |
E526272
|
entity |
| Predicate | hasPostalAbbreviation |
P43
|
FINISHED |
| Object | KY |
—
|
NE NERFINISHED |
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: KY | Statement: [Clinton County, Kentucky, hasPostalAbbreviation, KY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KY Context triple: [Clinton County, Kentucky, hasPostalAbbreviation, KY]
-
A.
KY
KY is the two-letter ISO 3166-1 alpha-2 country code for the Cayman Islands, a British Overseas Territory in the Caribbean.
-
B.
KY
KY is the vehicle registration code used on license plates for motor vehicles registered in County Kerry, Ireland.
-
C.
KY
KY is the abbreviation for the Judicial Commission of Indonesia, an independent state body responsible for overseeing the conduct and integrity of judges in the Indonesian judiciary.
-
D.
KY
KY is the postcode area covering Kirkcaldy and surrounding parts of eastern Scotland.
-
E.
KY
chosen
KY is the official United States Postal Service abbreviation for the state of Kentucky.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8a85274f481909e699b390bed9350 |
completed | April 22, 2026, 10:52 a.m. |
Created at: April 16, 2026, 4:44 p.m.