Domain-specific concept model for associating structured data that enables a natural language query

• US 20090171923A1
• Filed: 03/28/2008
• Published: 07/02/2009
• Est. Priority Date: 01/02/2008
• Status: Abandoned Application

• Current Assignee: Ben Rady, Craig Walls, Daniel L. James, Kelly Christopher Fox, Michael Patrick Nash, Paul Randolph Jr. Holser, Roderick F. Coffin III, Ruby Bailey, Ryan Scott Breidenbach
• Original Assignee: Ben Rady, Craig Walls, Daniel L. James, Kelly Christopher Fox, Michael Patrick Nash, Paul Randolph Jr. Holser, Roderick F. Coffin III, Ruby Bailey, Ryan Scott Breidenbach
• Inventors: Coffin, Roderick F. III, Breidenbach, Ryan Scott, Walls, Craig, Holser, Paul Randolph JR., Nash, Michael Patrick, Fox, Kelly Christopher, Rady, Ben, James, Daniel L., Bailey, Ruby
• Application Number:
  US12/079,792
• Publication Number:
  US 20090171923A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/3329 Natural language query formulation or dialogue systems

Abstract

The invention defines a domain specific concept model that is flexible, intuitive, and which easily integrates into disparate, but similarly architected, domain-specific databases. It is emphasized that this abstract is provided to comply with the rules requiring an abstract that will allow a searcher or other reader to quickly ascertain the subject matter of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. 37 CFR 1.72(b).

Claims

1. A domain-specific concept model architecture, comprising:

a plurality of concepts, each concept comprising at least one element, the plurality of concepts comprising a first concept and a second concept;

a plurality of relations, each relation defining how each concept relates to a property or an attribute, the plurality of relations comprising a first relation, a second relation, a third relation and a fourth relation;

each of the plurality of concepts having an identity associated with a macro meaning;

the first concept being logically mapped to the second concept via a first relation;

the second concept being logically mapped to the first concept via a second relation;

a plurality of attributes comprising a first attribute, each attribute defining information about the concept to which the attribute is related;

the first concept being logically mapped to a first attribute via a third relation;

the first attribute being logically mapped to the first concept via a fourth relation.

2. The architecture of claim 1 where the first concept is identifiable with at least one synonym.

3. The architecture of claim 1 where the first relation is identifiable with at least one synonym.

4. The architecture of claim 1 where the first relation is a verb phrase.

5. The architecture of claim 1 where the first attribute is identifiable with at least one synonym.

6. The architecture of claim 1 wherein the first concept is related to a first property value.

7. The architecture of claim 6 wherein the first property value has an equivalent property value identified by an alternative nomenclature.

8. The architecture of claim 1 wherein relations that relate concepts to concepts or concepts to attribute have corresponding reverse relations.

9. The architecture of claim 1 wherein the first concept and the second concept are mapped to a common external abstract, the first concept being mapped to the external abstract by a fifth relation, the second concept being mapped to the external abstract by a sixth relation.

10. The architecture of claim 6 wherein the first property value is an abstraction of an equivalent property value.

11. The architecture of claim 6 wherein the first property value is an abstraction of an equivalent property value, the equivalent property value being a natural language word.

12. The system of claim 1 wherein the first concept is a customer concept.

13. The system of claim 1 wherein the first concept is an order concept.

14. The system of claim 13 wherein the second concept is an employee concept having a sub-set property being a sales rep property.

15. The system of claim 14 wherein the first relation is defined as a “

written by”

relation, and the second relation is defined as a “

who wrote”

relation.

16. The system of claim 1 wherein the first attribute is a territory.

17. A domain-specific concept model architecture, comprising:

a plurality of concepts comprising a first concept and a second concept;

a plurality of relations, each relation defining how each concept relates to a property or an attribute, the plurality of relations comprising a first relation, a second relation, a third relation and a fourth relation;

each of the plurality of concepts having an identity associated with a macro meaning;

the first concept being logically mapped to the second concept via a first relation;

the second concept being logically mapped to the first concept via a second relation;

a plurality of attributes comprising a first attribute, each attribute defining information about the concept to which the attribute is related;

the first concept being logically mapped to a first attribute via a third relation;

the first attribute being logically mapped to the first concept via a fourth relation; and

the first concept defining a target concept;

whereby

data may be identified by a natural language query made against a target database.

18. The system of claim 17 wherein each relation between two concepts has a corresponding reverse-relationship associated therewith.

19. The system of claim 17 wherein the first concept is defined as a target concept.