LOTED: Exploiting Linked Data in Analyzing European Procurement Notices


Published on

presentation at the EKAW 2010 workshop on knowledge injection and extraction from linked data on http://loted.eu.

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Screenshot of the interface with something selected
  • Some RDF snippet
  • Some links
  • LOTED: Exploiting Linked Data in Analyzing European Procurement Notices

    1. 1. LOTED: Exploiting Linked Data in Analyzing European Procurement Notices<br />Francesco Valle, Mathieu d’Aquin, Tommaso Di Noiaand EnricoMotta<br />Technical University of Bari,<br />Electrical and Electronics Engineering Department Information Systems Research Group<br />francescovalle84@gmail.com, t.dinoia@poliba.it<br />Knowledge Media Institute, The Open University, Milton Keynes, UK<br />{m.daquin, e.motta}@open.ac.uk<br />
    2. 2. TED: European eProcurement<br />A portal with daily updates about tenders in <br />27 European countries<br />14 Sectors<br />All available in a collection of RSS feeds<br />
    3. 3.
    4. 4. TED<br />LOTED<br />Ontology<br />SPARQL<br />Endpoint<br />…<br />UK_Trans<br />CZ_Comp<br />DE_Agfo<br />SE_Educ<br />Every day: Updates from RSS feeds<br />Enriched RDF repr. of tenders<br />RDF representation of tenders<br />Linker<br />Entity<br />Reconciliation<br />New tender documents<br />RDFExtractor<br />geo-names<br />DBPedia<br />
    5. 5. http://loted.eu<br />
    6. 6. <rdf:Descriptionrdf:about="http://loted.eu/data/tender/295984-2010"> <br /> <rdf:typerdf:resource="http://loted.eu/ontology#Tender"/> <br /><loted:OJrdf:resource="http://loted.eu/data/officialJournal/194-2010"/> <br /><loted:ND>295984-2010</loted:ND> <br /> <loted:hasSectorrdf:resource="http://loted.eu/data/sector/tran"/> <br /><loted:PD>2010-10-06T00:00:00</loted:PD> <br /> <loted:hasSectorrdf:resource="http://loted.eu/data/sector/teeq"/> <br /><loted:CYrdf:resource="http://loted.eu/data/country/UK"/> <br /><loted:TWrdf:resource="http://sws.geonames.org/2653225/"/> <br /><loted:AUrdf:resource="http://loted.eu/data/authorityName/Royal_Mail_Group_Limited"/> <br /><loted:PRrdf:resource="http://loted.eu/data/procedure/2_-_Restricted_procedure"/> <br /><loted:OLrdf:resource="http://loted.eu/data/language/EN"/> <br /><loted:TDrdf:resource="http://loted.eu/data/document/7_-_Contract_award"/> <br /> <loted:PC>34911100_-_Trolleys</loted:PC> <br /><loted:hasSectorrdf:resource="http://loted.eu/data/sector/mapr"/> <br /><loted:ACrdf:resource="http://loted.eu/data/awardCriteria/2_-_The_most_economic_tender"/> <br /><loted:TYrdf:resource="http://loted.eu/data/typeOfBid/9_-_Not_applicable"/> <br /><loted:DS>2010-10-04T00:00:00</loted:DS> <br /><loted:NCrdf:resource="http://loted.eu/data/contract/2_-_Supply_contract"/> <br /><loted:HD>Member_states_-_Supply_contract_-_Contract_award_-_Restricted_procedure</loted:HD> <br /><loted:TI>UK-Chesterfield:_trolleys</loted:TI> <br /><loted:OC>34911100_-_Trolleys</loted:OC> <br /><loted:RPrdf:resource="http://loted.eu/data/regulation/4_-_European_Communities"/><br /></rdf:Description><br /><rdf:Descriptionrdf:about="http://loted.eu/data/authorityName/Royal_Mail_Group_Limited"> <br /><loted:IA>http://www.royalmailgroup.com/portal/rmg/jump1?catId=23200531&amp;amp;mediaId=23300561</loted:IA> <br /><loted:IA>www.royalmailgroup.com</loted:IA> <br /><loted:IA>www.royalmail.com</loted:IA> <br /><loted:IA>http://www.royalmailgroup.com</loted:IA> <br /><loted:IA>http://www.royalmail.com</loted:IA> <br /><rdfs:label>Royal Mail Group Limited</rdfs:label> <br /><rdf:typerdf:resource="http://loted.eu/ontology#4_-_Utilities"/> <br /> <rdf:typerdf:resource="http://loted.eu/ontology#6_-_Body_governed_by_public_law"/> <br /><rdf:typerdf:resource="http://loted.eu/ontology#8_-_Other"/> <br /></rdf:Description><br />
    7. 7. Some Details<br />Website:<br />http://loted.eu<br />SPARQL endpoint:<br />http://loted.eu:8081/LOTED1Rep/sparqlpage.jsp<br />URI scheme: <br />http://loted.eu/<data|ontology>/<type>/<ID><br />http://loted.eu/data/tender/295984-2010<br />http://loted.eu/ontology#Tender<br />http://loted.eu/data/authorityName/Royal_Mail_Group_Limited<br />http://loted.eu/data/country/UK<br />http://sws.geonames.org/2653225/ (Chesterfield, UK)<br />Triple store and query engine: Jena with TDB persistent storage.<br />Updated everyday<br />
    8. 8. But… <br />This is just another interface to the data<br />We could mostly have done the same with a database and some geolocation<br />It is not so useful in terms of data analysis<br />We have not learn much, we have no new knowledge<br />We have not really used the links<br />
    9. 9. So…<br />Try mine Data+Links+LOD<br />Discover knowledge in the connection between the local data and LOD datasets<br />A first step: visual interface for data analysis based on “dimensions” coming both from the local data and from external data<br />
    10. 10. Tender profiles<br />
    11. 11. Generating data overviews<br />Ranking criteria<br />Distribution of the data<br />
    12. 12. Using the links…<br />Tender profiles dependent on a DBPedia property for the city in which the tender is<br />2 examples<br />A general approach<br />
    13. 13. Using the region from DBPedia<br />Can also do manual ranking (e.g., north to south, east to west)<br />
    14. 14. Using the political party from DBPedia<br />Becomes crucial to assess the bias introduced by incomplete data/lack of coverage<br />
    15. 15. Lessons Learned – Linked Data <br />Extracting new data from the connection with external linked datasets is feasible <br />And Valuable<br />But is hard because<br />The “Linked Data Infrastructure” is not ready: entity reconciliation, linking basic sameAs reasoning… <br />Still difficult to find “exploitable” data, and this is only the first step of the challenge<br />
    16. 16. Lessons Learned – Extracting knowledge from linked data <br />New challenges:<br />You don’t know what you will get<br />You don’t know how much you will get<br />You don’t know if what you get is good<br />How do we match to user need?<br />How can we reduce the effort in finding extracting something which might not be useful?<br />How can we discover what needs to be discover?<br />
    17. 17. Next Steps<br />More advanced knowledge discovery techniques<br />Detecting trends <br />Identifying automatically the relevant dimensions<br />Using more links<br />Using the links more!<br />Investigate the specific challenges of Knowledge Discovery from Linked Data<br />
    18. 18. Thank You!<br />m.daquin@open.ac.uk<br />@mdaquin<br />