Update Add Triple

[prasmussen15]

Summary

Brief description of the changes in this PR.

Type of Change

• Bug fix
• New feature
• Performance improvement
• Documentation/Tests

Objective

For new features and performance improvements: Clearly describe the objective and rationale for this change.

Testing

• Unit tests added/updated
• Integration tests added/updated
• All existing tests pass

Breaking Changes

• This PR contains breaking changes

If this is a breaking change, describe:

• What functionality is affected
• Migration path for existing users

Checklist

• Code follows project style guidelines (make lint passes)
• Self-review completed
• Documentation updated where necessary
• No secrets or sensitive information committed

Related Issues

Closes #[issue number]

[claude]

Critical Issues

1. Potential Runtime Error with None UUID

The refactored code removes the explicit 'if source_node.uuid is not None' check before calling EntityNode.get_by_uuid(). While the Node.uuid field is typed as str (not optional), Pydantic models can still have None values if explicitly set or constructed improperly.

If source_node.uuid or target_node.uuid is None, the code will likely fail with an unexpected error (possibly a database query error or type error) rather than cleanly falling back to resolve_extracted_nodes().

2. Changed Error Handling Behavior

Old behavior: If a node with a specified UUID doesn't exist, raise a ValueError with a clear message
New behavior: Silently fall back to resolve_extracted_nodes()

This is a significant behavioral change that could mask bugs. If a user explicitly provides a UUID expecting to reference an existing node, they should be notified if that node doesn't exist, not have the system silently create/resolve a different node.

3. Missing Test Coverage

No tests were found for the add_triplet method. This method appears to be a public API but lacks test coverage to validate:

• Behavior when nodes exist vs don't exist
• Behavior when UUIDs are None vs valid vs invalid
• The fallback to resolve_extracted_nodes()

4. Incomplete PR Description

The PR template is not filled out. For a behavioral change like this, it should clearly document:

• What bug is being fixed or what feature is being added
• Why the change is needed
• The rationale for changing error handling behavior

Recommendations

1. Preserve the None check or add validation at the method start
2. Reconsider the error handling change - falling back silently may not be the desired behavior
3. Add comprehensive tests for this method
4. Fill out the PR template to explain the motivation for this change