Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate star:E13_sdhss_P17 star #4

Open
lu-pl opened this issue Sep 24, 2024 · 0 comments
Open

Investigate star:E13_sdhss_P17 star #4

lu-pl opened this issue Sep 24, 2024 · 0 comments

Comments

@lu-pl
Copy link
Collaborator

lu-pl commented Sep 24, 2024

The construct query for generating star:E13_sdhss_P17 starlegs assertions finds the common connector in the star pattern and isolates the connected E13 nodes that do not have P14/P17 assertions pointing to the same objects as the initial E13. The problem with star:E13_sdhss_P17 is that lots of the E13 nodes turn out to actually have P14/P17 assertions already attached to them.

construct {
    ?o crm:P14_carried_out_by ?agent .
    ?o crm:P17_was_motivated_by ?source .
}
where {
    ?e13_initial a star:E13_sdhss_P17 ;
    	crm:P140_assigned_attribute_to ?common .

    optional {?e13_initial crm:P14_carried_out_by ?agent}
    optional {?e13_initial crm:P17_was_motivated_by ?source}

    ?common ^crm:P140_assigned_attribute_to ?o .
    filter (?o != ?e13_initial)

    minus {?o crm:P14_carried_out_by ?agent}
    minus {?o crm:P17_was_motivated_by ?source}
}

The reason why the connected E13s do not get subtracted in the MINUS clauses is that their P14/P17 assertions point to other objects than the initial E13. So running the above construct query would generate additional P14/P17 for almost all matches.

This should be investigated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant