Cyc Subject Predicate Object

1. Here's my first cut at organizing all those
first-level concepts in the Cyc hierarchy.
Looks like we should call this one an
Entity-Relation-Proposition hierarchy.

# <html><xmp>
# KEHOME/kb/spo.cyc
# Feb/15/2007

begin hierarchy Entity-Relation-Proposition;
Thing;
# entity
/  Entity;
/  IndexicalConcept;
/  Individual;
//     TemporalThing;
///     SomethingExistiing;
////         Entity;
/  Intangible;
/  PartiallyIntangible;
/  PartiallyTangible;
/  TangibleThing;

# characteristic
/  Relation;
//      FixedArityRelation;
///         BinaryRelation;
////             Property;

# context
/  Microtheory;
# proposition
/  CycLQuery;
/  CycLTerm;
/  DocumentationConstant;
/  ELSentence-Assertible;
/  ELTemplate;
/  ELVariable;
/  Path-Generic;
/  PathSystem;
/  ReformulatorHighlyRelevantFORT;
/  ReformulatorIrrelevantFORT;
/  SubLSymbol;
/  TheTerm;

# group
/  SetOrCollection;
// Collection;
///     Class;
///     CoreConstant;
// Set-Mathematical;
end hierarchy Entity-Relation-Proposition;

begin hierarchy imaginary;
Nothing;
end hierarchy imaginary;

# propositions
# Thing      has Property = Value;
# individual isu class;
# species    iss genus;
(#$Property #$Thing #$Value);
(#$isa individual class);
(#$genls species genus);

# mKR relation CycL
nonexistent is Nothing;
existent is Thing;
#  entity is Entity;
#  characteristic is Relation;
#  proposition is Proposition;
# isu is isa;
# iss is genls;
#</xmp></html>

2. I'm still looking at the internals of the ERP hierarchy.
I've found more Collections, and lots of Type classes.
I think all these Type classes have the same error -- using
"isu","iss" relations instead of "ismem" relations.  I'm not 
aware of any reason for having these Type classes.
My guess, pending further investigation, is that all the
Type classes should be removed from the hierarchy.

Dick McCullough
knowledge := man do identify od existent done;
knowledge haspart proposition list;
http://mKRmKE.org/

Received on Thursday, 15 February 2007 11:02:37 UTC