Triple
T34508295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KY-01 |
E885947
|
entity |
| Predicate | usesPostalStateCode |
P89904
|
FINISHED |
| Object | KY |
—
|
LITERAL 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: [KY-01, usesPostalStateCode, KY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPostalStateCode Context triple: [KY-01, usesPostalStateCode, KY]
-
A.
postalState
Indicates the state or province associated with an entity’s postal or mailing address.
-
B.
hasPostalAbbreviationState
Indicates that a state is associated with a specific standardized postal abbreviation.
-
C.
postalStateCode
chosen
Indicates the standardized state or regional code used in a postal address for the entity.
-
D.
hasPostalAbbreviationProvince
Indicates that a province is associated with a specific standardized postal abbreviation used in mailing addresses.
-
E.
hasPostalAssociationWith
Indicates a relationship in which one entity is connected to another through postal services, such as mail handling, delivery, routing, or shared postal operations.
- F. None of above.
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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 2:01 a.m.