While the OpenZeppelin Beacon Proxy pattern isn't explicitly used in the core contracts, it does serve as the architectural inspiration for the contracts that define the market operations for each individual land parcel on the Geo Web.
An overview of OpenZeppelin's Beacon Proxy pattern can be found at https://docs.openzeppelin.com/contracts/3.x/api/proxy#beacon.
At a high level, the design challenge was to be able to accommodate a separate instance of the
BeaconDiamond contract for each land parcel on the Geo Web while maintaining upgradability without requiring iteratative changes to each instance.
This is what the Beacon Proxy is designed to do. So, we combined it with the Diamonds Multi-Facet Proxy standard for our own hybrid implementation.