4 ms·

That’s a great example and I understand it was intentionally simple but highlighted how LLMs need care with use. Not that this example is very related to NLP:

That’s a great example and I understand it was intentionally simple but highlighted how LLMs need care with use. Not that this example is very related to NLP: My prompt: `<>` The response: ``` { "origin": ["PDX"], "destination": ["HAV"], "date": "2025-04-01", "departure_time": null, "preferences": null } ``` Of course I meant Portland Maine (PWM), there is more than one airport option in Cuba than HAV, and it got the date wrong, since Easter is April 20 this year.

scarface_74 2y ago
If the business stakeholders came out with that scenario, I would modify the prompt like this. You would know the users address if they had an account. https://chatgpt.com/share/678c1708-639c-8010-a6be-9ce105570302 https://chatgpt.com/share/678c1708-639c-8010-a6be-9ce1055703...
- LeafItAlone 2y ago
 OK, but that only fixed one of the three issues.
 - scarface_74 2y ago
 While the first one is easy. I mean you could give it a list of holidays and dates. But the rest you would just ask the user to confirm the information and say “is this correct”? If they say “No” ask them which isn’t correct and let them correct it. I would definitely assume someone wanted to leave from an airport close by if they didn’t say anything. You don’t want the prompt to grow too much. But you do have analytics that you can use to improve your prompt. In the case of Connect, you define your logic using a GUi flowchart builder called a contact flow. BTW: with my new prompt, it did assume the correct airport “<>”
 - LeafItAlone 2y ago
 Sure, all the problems are “easy” once you identify them. As with most products. But the majority of Show HN posts here relying on LLMs that I see don’t account for simple things like my example. Flights finders in particular have been pretty bad. >BTW: with my new prompt, it did assume the correct airport “<>” Not really. It chose the airport you put basically in the prompt. But I don’t live in MA, I live closer to PDX. And it didn’t suggest the multiple other Cuba airports. So you’ll end up with a lot of guiding rules.
 - scarface_74 2y ago
 A human would assume if you said “Portland” they would first assume you meant PDX unless they looked up your address and then they would assume Maine. Just like if I said I wanted to fly to Albany, they would think I meant New York and not my parents city in south GA (ABY) which only has three commercial flights a day. Even with a human agent, you ask for confirmation. Also, I ask to speak to people on the ground - in this case it would be CSRs - to break it. That’s another reason I think “side projects” are useless and they don’t have any merit on resumes. I want them to talk about real world implementations.

scarface_74 2y ago

If the business stakeholders came out with that scenario, I would modify the prompt like this. You would know the users address if they had an account. https://chatgpt.com/share/678c1708-639c-8010-a6be-9ce105570302 https://chatgpt.com/share/678c1708-639c-8010-a6be-9ce1055703...

LeafItAlone 2y ago
OK, but that only fixed one of the three issues.
- scarface_74 2y ago
 While the first one is easy. I mean you could give it a list of holidays and dates. But the rest you would just ask the user to confirm the information and say “is this correct”? If they say “No” ask them which isn’t correct and let them correct it. I would definitely assume someone wanted to leave from an airport close by if they didn’t say anything. You don’t want the prompt to grow too much. But you do have analytics that you can use to improve your prompt. In the case of Connect, you define your logic using a GUi flowchart builder called a contact flow. BTW: with my new prompt, it did assume the correct airport “<>”
 - LeafItAlone 2y ago
 Sure, all the problems are “easy” once you identify them. As with most products. But the majority of Show HN posts here relying on LLMs that I see don’t account for simple things like my example. Flights finders in particular have been pretty bad. >BTW: with my new prompt, it did assume the correct airport “<>” Not really. It chose the airport you put basically in the prompt. But I don’t live in MA, I live closer to PDX. And it didn’t suggest the multiple other Cuba airports. So you’ll end up with a lot of guiding rules.
 - scarface_74 2y ago
 A human would assume if you said “Portland” they would first assume you meant PDX unless they looked up your address and then they would assume Maine. Just like if I said I wanted to fly to Albany, they would think I meant New York and not my parents city in south GA (ABY) which only has three commercial flights a day. Even with a human agent, you ask for confirmation. Also, I ask to speak to people on the ground - in this case it would be CSRs - to break it. That’s another reason I think “side projects” are useless and they don’t have any merit on resumes. I want them to talk about real world implementations.