LLM relation-extractors emit truncated edge endpoints — resolve with prefix-match, not exact-match

A two-stage LLM extraction pipeline (stage 1 produces nodes with FULL descriptions; stage 2 produces edges that reference their endpoints BY description) commonly caps the edge-endpoint description length in the stage-2 prompt (e.g. "keep endpoint descriptions under ~80 chars"). As a result, an edge's fromDescription/toDescription is often a TRUNCATED PREFIX of the corresponding node's full description. If you later build a graph payload and resolve each edge's endpoints to node ids by an EXACT (type, description) match, a large fraction of edges silently fail to resolve and get dropped: the nodes ingest fine but the resulting graph has almost no edges — and nothing errors, so it's easy to miss.