Edit Paper: Zhishi.links Results for OAEI 2011

Jump to: navigation, search

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.


Zhishi.links Results for OAEI 2011

Abstract[edit]

[[has abstract:={{{Abstract}}}]]

Conclusion[edit]

[[has conclusion:={{{Conclusion}}}]]

Future work[edit]

[[has future work:={{{Future work}}}]]

Approach[edit]

Positive Aspects: [[Has PositiveAspects::{{{PositiveAspects}}}]]

Negative Aspects: [[Has NegativeAspects::{{{NegativeAspects}}}]]

Limitations: [[Has Limitations::{{{Limitations}}}]]

Challenges: [[Has Challenges::{{{Challenges}}}]]

Proposes Algorithm: [[Proposes Algorithm::{{{ProposesAlgorithm}}}]]

Methodology: [[uses Methodology::{{{Methodology}}}]]

Requirements: [[Has Requirements::{{{Requirements}}}]]

Limitations: [[Has Limitations::{{{Limitations}}}]]

Implementations[edit]

Download-page: [[Has Downloadpage::{{{Download-page}}}]]

Access API: [[access API::{{{API}}}]]

Information Representation: [[Has InfoRepresentation::{{{InfoRepresentation}}}]]

Data Catalogue: [[Has DataCatalouge::{{{Catalogue}}}]]

Runs on OS: [[ runsOn OS::{{{OS}}}]]

Vendor: [[Has vendor::{{{vendor}}}]]

Uses Framework: [[Uses Framework::{{{Framework}}}]]

Has Documentation URL: [[Has DocumentationURL::{{{DocumentationURL}}}]]

Programming Language: [[implementedIn ProgLang::{{{ProgLang}}}]]

Version: [[has Version ::{{{Version}}}]]

Platform: [[has platform::{{{Platform}}}]]

Toolbox: [[uses Toolbox::{{{Toolbox}}}]]

GUI: has GUI::No

Research Problem[edit]

Subproblem of: [[Has Subproblem::{{{Subproblem}}}]]

RelatedProblem: [[Has relatedProblem::{{{RelatedProblem}}}]]

Motivation: [[Has motivation::{{{Motivation}}}]]

Evaluation[edit]

Experiment Setup: [[Has ExperimentSetup::{{{ExperimentSetup}}}]]

Evaluation Method : [[Has EvaluationMethod::{{{EvaluationMethod}}}]]

Hypothesis: [[Has Hypothesis::{{{Hypothesis}}}]]

Description: [[Has Description::{{{Description}}}]]

Dimensions: [[Has Dimensions::{{{Dimensions}}}]]

Benchmark used: [[has Benchmark::{{{Benchmark}}}]]

Results: [[Has Results::{{{Results}}}]]


[edit]
Paper Title*: Full title of the given paper
Subject: Primary subject or topic of research of the paper.
Author(s):
Publication venue: Publication venue of the paper.
Year: The year in which the paper is published.
Keywords:
Abstract: Abstract of the paper.
Conclusion:
Future work: Future ideas of the paper.
Problem: The research problem.
Approach: Approach used to achieve the goal.
Implementation: The implementation/framework that is invoked when running.
Evaluation: Proposed work Evaluation.
Positive Aspects:
Negative Aspects:
Limitations:
Challenges:
Proposes Algorithm:
Proposes Model:
Methodology:
Requirements:
Download-page:
Access API:
Information Representation:
Data Catalogue:
OS:
Vendor: Organization: commercial, free or otherwise
Uses Framework: Framework name
Documentation URL: Link to Documentation webpage.
Programming Language:
Version:
Platform:
Toolbox:
GUI: whether the implementation has a GUI?
Subproblem of: A broader research problem.
Related Problem: A another research problem.
Motivation: The motivation to solve the problem.


Experiment setup:
Evaluation method : A broader research problem.
Hypothesis: A another research problem.
Description: The motivation to solve the problem.
Dimensions:
Select evaluation dimension.
Benchmark: Benchmark used for evaluation.
Results:



Paper description:

Cancel

Access APINo data available now. +
Event in seriesOM +
Has BenchmarkDBpedia +, Freebase + and GeoNames +
Has Challenges– When it comes with the problem of homony
– When it comes with the problem of homonyms, instance matching systems should exploit as much information as possible to enhance the discriminability of their matchers. Currently, subject to the fact that most descriptions given by New York Times are written in natural language, the performance of our semantic similarity calculator are constrained. We are considering more tests carrying out on datasets in different styles and designing a more robust system. – In DI track, only three types of resources are involved. The special words in names, which are extracted as values of characteristic properties, are chosen manually. Some smarter strategies should be applied to accomplish this mission.
uld be applied to accomplish this mission. +
Has DataCatalouge{{{Catalogue}}} +
Has DescriptionNo data available now. +
Has DimensionsAccuracy +
Has DocumentationURLhttp://No data available now. +
Has Downloadpagehttp://apex.sjtu.edu.cn/apex wiki/Zhishi.links +
Has EvaluationAccuracy Evaluation +
Has EvaluationMethodUtilize distributed MapReduce framework to adopt index-based pre-matching +
Has ExperimentSetupTests were carried out on a Hadoop computer cluster. Each node has a quad-core Intel Core 2 processor (4M Cache, 2.66 GHz), 8GB memory. The number of reduce tasks was set to 50. +
Has GUINo +
Has HypothesisNo data available now. +
Has ImplementationZhishi.links +
Has InfoRepresentationNo data available now. +
Has LimitationsNo data available now. +
Has NegativeAspectsNo data available now. +
Has PositiveAspectsNo data available now. +
Has RequirementsNo data available now. +
Has ResultsNo data available now. +
Has SubproblemNo data available now. +
Has VersionNo data available now. +
Has abstractThis report presents the results of Zhishi
This report presents the results of Zhishi.links, a distributed instance matching system, for this year’s Ontology Alignment Evaluation Initiative (OAEI) campaign. We participate in Data Interlinking track (DI) of IM@OAEI2011. In this report, we briefly describe the architecture and matching strategies of Zhishi.links, followed by an analysis of the results.
s, followed by an analysis of the results. +
Has approachNo data available now. +
Has authorsXing Niu +, Shu Rong +, Yunlong Zhang + and Haofen Wang +
Has conclusionIn this report, we have presented a brief
In this report, we have presented a brief description of Zhishi.links, an instance matching system. We have introduced the architecture of our system and specific techniques we used. Also, the results have been analyzed in detail and several guides for improvements have been proposed.
uides for improvements have been proposed. +
Has future workWe look forwards to build an instance matching system with better performance and higher stability in the future. +
Has motivationNo data available now. +
Has platformNo data available now. +
Has problemLink Discovery +
Has relatedProblemNo data available now. +
Has subjectOntology Alignment +
Has vendorNo data available now. +
Has year2011 +
ImplementedIn ProgLangNo data available now. +
Proposes AlgorithmNo data available now. +
RunsOn OSNo data available now. +
TitleZhishi.links Results for OAEI 2011 +
Uses FrameworkNo data available now. +
Uses MethodologyNo data available now. +
Uses ToolboxNo data available now. +