I am working on a project where we use java to load rdf files to graphdb. We are working on moving to the cloud and I am noticing that the data in graphdb from the original environment vs the cloud/docker environment are different. Specifically, there is a class in the owl file that is owl:equivalentClass (Construct) to another class (Health_Status) that is not showing in the original results. I think it has something to do with the inferencing, but I am using owl-horst (optimized) for the ruleset and enable consistency checks marked for both of them and they are both 10.6.2 versions of graphdb. The only change in the code is that the owl file is loaded through resources rather than a directory on the server. Shown below is the class "construct" that should not be in the results. Unfortunately, I did not set up the original code and I am not sure exactly how the owl file works either, but I have been doing research and I dont believe I can change the tag to rdf:subClassOf like the others are. Is there a chance it is a code issue rather than a graphdb issue?

This is the docker-compose file for graphdb

  graphdb:
    container_name: graphdb
    build:
      context: .
      dockerfile: Dockerfile
      args:
        version: 10.6.2
    restart: unless-stopped
    environment: 
      GDB_JAVA_OPTS: >-
        -Dgraphdb.home=/opt/graphdb/home
        -Dgraphdb.workbench.importDirectory=/opt/graphdb/home/graphdb-import
        -Dgraphdb.workbench.cors.enable=true
        -Denable-context-index=true
        -Dentity-pool-implementation=transactional
        -Dhealth.max.query.time.seconds=60
        -Dgraphdb.append.request.id.headers=true
        -Dreuse.vars.in.subselects=true
    ports: 
      - 7200:7200
      - 7300:7300
    volumes:
      - ./graphdb-data:/opt/graphdb/home

Does anything in there stand out that could cause this? Alternatively, what would be the query to delete all of these?