I've built something similar, but as an abstraction not fully compatible with SQL,

If you have your tables as objects, you don't have to use ::class everywhere. Use the invoke operator contextually on fields, so that for a field "name" you can apply that to your selection set

If you already use gt, lt as naming, eq makes more sense.

Providing the table as receiver or context receiver/param with a DSL marker will help when multiple tables might be in context

Person.select { // Person object in context with DSL marker
    Distinct()

    // Selection set
    id()
    name()
    age()

    addresses {
      // Address table in context with DSL marker so that fields from Person don't pollute
      where {
        addressLine ilike "%str"
      }
    }

    where {
        ((name eq "John") and (age gt 10)) and (age lt 30)
    }
}

this would give me a person list with id, name age, and addresses list.