I’m not familiar with GraalVM architecture or build structure, but if I had to guess I’d strongly expect any single executable (as currently found in some babashka distributions) to be considered statically linked artifact.
If I’d have to guess further I’d expect – from parts talking about “Corresponding Application Code” in [1] – that making whole application source available would satisfy requirement of replaceability (while LGPL FAQ currently explicitly says object code is required [2], I reckon its wording is not precise enough, at least I cannot derive requirement for object code or other intermediate build artifacts from the license itself).
One more thing to consider is that simply linking to resources which are not under your control might not be enough to satisfy licensing terms (see e.g. discussion under [3]).
Fwiw hth 
[1] https://www.gnu.org/licenses/lgpl-3.0.txt
[2] Frequently Asked Questions about the GNU Licenses - GNU Project - Free Software Foundation
[3] licensing - How long do I have to provide the source code for a LGPL-library? - Software Engineering Stack Exchange