2002
DOI: 10.1007/3-540-45810-7_34
|View full text |Cite
|
Sign up to set email alerts
|

MnM: Ontology Driven Semi-automatic and Automatic Support for Semantic Markup

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
107
0
13

Year Published

2003
2003
2009
2009

Publication Types

Select...
4
2
2

Relationship

2
6

Authors

Journals

citations
Cited by 189 publications
(120 citation statements)
references
References 9 publications
0
107
0
13
Order By: Relevance
“…Ideally, what is required is a knowledge extraction capability in which relevant domain knowledge can be automatically extracted from source documents. We are currently exploring an ability to augment textual resources with semantic annotations in order to identify the entities contained in the resource document [38,39]; however, we also intend to explore an additional capability for the extraction of relational information. While the extraction of relational information is significantly more complex than entity recognition, the advantage of the technique is that it provides a much richer substrate for information fusion and knowledge processing, especially in situations where information content is dispersed across multiple source documents.…”
Section: Content Acquisitionmentioning
confidence: 99%
“…Ideally, what is required is a knowledge extraction capability in which relevant domain knowledge can be automatically extracted from source documents. We are currently exploring an ability to augment textual resources with semantic annotations in order to identify the entities contained in the resource document [38,39]; however, we also intend to explore an additional capability for the extraction of relational information. While the extraction of relational information is significantly more complex than entity recognition, the advantage of the technique is that it provides a much richer substrate for information fusion and knowledge processing, especially in situations where information content is dispersed across multiple source documents.…”
Section: Content Acquisitionmentioning
confidence: 99%
“…iii) By information extraction -we also have used a dedicated tool -MnM [27] developed in-house, which enables information extraction engines, such as Amilcare [4] to be integrated with the Magpie knowledge model component.…”
Section: Before Deploying Magpiementioning
confidence: 99%
“…MnM [27], is a tool, which incorporates a web browser and interfaces to web based ontology libraries and to information extraction engines. MnM enables users to attach information extraction mechanisms to ontological classes.…”
Section: Before Deploying Magpiementioning
confidence: 99%
See 1 more Smart Citation
“…For instance, the Amaya editor implementing the Annotea framework [15], the CREAM-based Ont-O-Mat/Annotizer [13], MnM [24], and the SHOE framework [14]. The main difference between these efforts and the approach taken by Magpie and KIM lies in the origin of the annotations.…”
Section: Related Workmentioning
confidence: 99%