diff --git a/docs/release_notes/1386-numericValue b/docs/release_notes/1386-numericValue
new file mode 100644
index 00000000..c0f68f7c
--- /dev/null
+++ b/docs/release_notes/1386-numericValue
@@ -0,0 +1,4 @@
+### Major Updates
+
+- Simplified the range of `gist:numericValue`. Issue [#1386](https://github.com/semanticarts/gist/issues/1386).
+
diff --git a/ontologies/gistCore.ttl b/ontologies/gistCore.ttl
index 2f1ff1da..04178d97 100644
--- a/ontologies/gistCore.ttl
+++ b/ontologies/gistCore.ttl
@@ -3116,28 +3116,16 @@ gist:numericValue
 	rdfs:range [
 		a rdfs:Datatype ;
 		owl:unionOf (
-			xsd:byte
 			xsd:decimal
 			xsd:double
 			xsd:float
-			xsd:int
 			xsd:integer
-			xsd:long
-			xsd:negativeInteger
-			xsd:nonNegativeInteger
-			xsd:nonPositiveInteger
-			xsd:positiveInteger
-			xsd:short
-			xsd:unsignedByte
-			xsd:unsignedInt
-			xsd:unsignedLong
-			xsd:unsignedShort
 			owl:rational
-			owl:real
 		) ;
 	] ;
 	skos:definition "The actual value of a magnitude."^^xsd:string ;
 	skos:prefLabel "numeric value"^^xsd:string ;
+	skos:scopeNote "Caution is advised when using the xsd:float, xsd:integer, or owl:rational datatypes. The xsd:float datatype is less precise than xsd:double, and not recommended unless the source data is xsd:float or if precision is not as important as the size of the data or speed of computation. Some downstream applications might be limited to using the 32-bit xsd:int datatype instead of xsd:integer; if so, check to see that the xsd:integer values being passed downstream are within the 32-bit range. Some triplestores cannot do math using values of the owl:rational datatype."^^xsd:string ;
 	.
 
 gist:occursIn