HOUSE_OVERSIGHT_013170.jpg
1.39 MB
Extraction Summary
0
People
2
Organizations
0
Locations
0
Events
0
Relationships
2
Quotes
Document Information
Type:
Technical/academic manuscript (page 254)
File Size:
1.39 MB
Summary
This document is page 254 of a technical manuscript titled '13 Local, Global and Glocal Knowledge Representation.' It details technical specifications for an AI system, specifically discussing 'Procedure Nodes' (SchemaNode, PredicateNode) and 'HebbianLinks' within the context of the OpenCog artificial intelligence framework. The document bears a 'HOUSE_OVERSIGHT' Bates stamp, indicating it was likely gathered as evidence during a congressional investigation, possibly related to Epstein's funding of scientific research or AI projects.
Organizations (2)
| Name | Type | Context |
|---|---|---|
| OpenCog |
Mentioned in section 13.3.7 regarding Atom types and data usage.
|
|
| House Oversight Committee |
Implied by the Bates stamp 'HOUSE_OVERSIGHT_013170' at the bottom right.
|
Key Quotes (2)
"The asymmetric HebbianLink indicates that when the first argument is present in a situation, the second is also often present."Source
HOUSE_OVERSIGHT_013170.jpg
Quote #1
"Finally, there are also Atom types referring to specific types of data important to using OpenCog in specific contexts."Source
HOUSE_OVERSIGHT_013170.jpg
Quote #2
Full Extracted Text
Complete text extracted from the document (2,070 characters)
254
13 Local, Global and Glocal Knowledge Representation
13 Local, Global and Glocal Knowledge Representation
The asymmetric HebbianLink indicates that when the first argument is present in a situation,
the second is also often present. The symmetric (default) version indicates that this relationship
holds in both directions. The inverse versions indicate the negative relationship: e.g. when one
argument is present in a situation, the other argument is often not present.
the second is also often present. The symmetric (default) version indicates that this relationship
holds in both directions. The inverse versions indicate the negative relationship: e.g. when one
argument is present in a situation, the other argument is often not present.
13.3.6 Procedure Nodes
There are nodes representing various sorts of procedures; these are kinds of ProcedureNode,
e.g.
e.g.
• SchemaNode, indicating any procedure
• GroundedSchemaNode, indicating any procedure associated in the system with a Combo
program or C++ function allowing the procedure to be executed
• PredicateNode, indicating any predicate that associates a list of arguments with an output
truth value
• GroundedPredicateNode, indicating a predicate associated in the system with a Combo
program or C++ function allowing the predicate’s truth value to be evaluated on a given
specific list of arguments
• GroundedSchemaNode, indicating any procedure associated in the system with a Combo
program or C++ function allowing the procedure to be executed
• PredicateNode, indicating any predicate that associates a list of arguments with an output
truth value
• GroundedPredicateNode, indicating a predicate associated in the system with a Combo
program or C++ function allowing the predicate’s truth value to be evaluated on a given
specific list of arguments
ExecutionLinks and EvaluationLinks record the activity of SchemaNodes and PredicateN-
odes. We have seen many examples of EvaluationLinks in the above. Example ExecutionLinks
would be:
odes. We have seen many examples of EvaluationLinks in the above. Example ExecutionLinks
would be:
ExecutionLink step\_forward
ExecutionLink step\_forward 5
ExecutionLink
+
ListLink
NumberNode: 2
NumberNode: 3
ExecutionLink step\_forward 5
ExecutionLink
+
ListLink
NumberNode: 2
NumberNode: 3
The first example indicates that the schema "step forward" has been executed. The second
example indicates that it has been executed with an argument of "5" (meaning, perhaps, that 5
steps forward have been attempted). The last example indicates that the "+" schema has been
executed on the argument list (2,3), presumably resulting in an output of 5.
example indicates that it has been executed with an argument of "5" (meaning, perhaps, that 5
steps forward have been attempted). The last example indicates that the "+" schema has been
executed on the argument list (2,3), presumably resulting in an output of 5.
The output of a schema execution may be indicated using an ExecutionOutputLink, e.g.
ExecutionOutputLink
+
ListLink
NumberNode: 2
NumberNode: 3
+
ListLink
NumberNode: 2
NumberNode: 3
refers to the value "5" (as a NumberNode).
13.3.7 Links for Special External Data Types
Finally, there are also Atom types referring to specific types of data important to using OpenCog
in specific contexts.
in specific contexts.
HOUSE_OVERSIGHT_013170
Discussion 0
No comments yet
Be the first to share your thoughts on this epstein document