Triple
T2419330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin County, Kentucky |
E52381
|
entity |
| Predicate | postalAbbreviation |
P43
|
FINISHED |
| Object | KY |
E251520
|
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: KY | Statement: [Franklin County, Kentucky, postalAbbreviation, KY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KY Context triple: [Franklin County, Kentucky, postalAbbreviation, KY]
-
A.
KY
chosen
KY is the official United States Postal Service abbreviation for the state of Kentucky.
-
B.
KY
KY is the postcode area covering Kirkcaldy and surrounding parts of eastern Scotland.
-
C.
KE
KE is the two-letter ISO 3166-1 alpha-2 country code assigned to Kenya for international identification and data standards.
-
D.
KE
KE is the IATA airline designator for Korean Air, the flag carrier and largest airline of South Korea.
-
E.
KA
KA is the vehicle registration code used on license plates for cars registered in the German city of Karlsruhe.
- 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc96e1b3881909de57501b5d4099a |
completed | March 7, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aebf5397508190b755e522060041c0 |
completed | March 9, 2026, 12:38 p.m. |
Created at: March 6, 2026, 9:42 p.m.