Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of relevant examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of relevant examples for a BP is not clearly delineated anywhere.

The solution to an "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to such a rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can often be labelled "allsorted", since the pool of all relevant examples just amounts to the two unrelated sides. But some "gap" Bongard Problems are not like that, and there are more related classes of examples than the two shown, left unsorted.

NOTE: Sometimes the class of all examples in a Bongard Problem is imprecise, but, despite that, the underlying rule is precise--say, for some potential new example, it is unclear whether it should be included in the Bongard Problem at all, but, if it were included, it would be clear where it should be sorted. Should a Bongard Problem like this be called "allsorted" or not? It is fuzziness in the class of relevant examples, but not the rule. Perhaps this should be its own independent keyword. - Aaron David Fairbanks, Nov 23 2021

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of relevant examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of relevant examples for a BP is not clearly delineated anywhere.

The solution to an "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to such a rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can often be labelled "allsorted", since the pool of all relevant examples just amounts to the two unrelated sides. But some "gap" Bongard Problems are not like that, and there are more related classes of examples than the two shown, left unsorted.

NOTE: Sometimes the class of all examples in a Bongard Problem is imprecise, but, despite that fact, the underlying rule is precise--say, for some potential new example, it is unclear whether it should be included in the Bongard Problem at all, but, if it were included, it would be clear where it should be sorted. Should a Bongard Problem like this be called "allsorted" or not? It is fuzziness in the class of relevant examples, but not the rule. Perhaps this should be its own independent keyword. - Aaron David Fairbanks, Nov 23 2021

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of relevant examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of relevant examples for a BP is not clearly delineated anywhere.

The solution to an "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to such a rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can often be labelled "allsorted", since the pool of all relevant examples just amounts to the two unrelated sides. But some "gap" Bongard Problems are not like that, and there are more related classes of examples than the two shown, left unsorted.

NOTE: Sometimes the class of all examples in a Bongard Problem is imprecise, but, despite that fact, the underlying rule is precise--say, for some potential new example, it is unclear whether it should be included in the Bongard Problem at all, but, if it were included, it would be clear where it should be sorted. Should a Bongard Problem like this be called "allsorted" or not? It is fuzziness in the class of relevant examples, but not the rule. Perhaps this should be its own keyword. - Aaron David Fairbanks, Nov 23 2021

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of relevant examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of relevant examples for a BP is not clearly delineated anywhere.

The solution to an "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to such a rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can often be labelled "allsorted", since the pool of all relevant examples just amounts to the two unrelated sides. But some "gap" Bongard Problems are not like that, and there are more related classes of examples than the two shown, left unsorted.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of relevant examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of relevant examples for a BP is not clearly delineated anywhere.

The solution to an "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to such a rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can often be labelled "allsorted", since the pool of all relevant examples just amounts to the two unrelated sides. But some "gap" Bongard Problems are not "allsorted", since there are more related classes of examples than the two shown, left unsorted.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of relevant examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of relevant examples for a BP is not clearly delineated anywhere.

The solution to an "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can often be labelled "allsorted", since the pool of all relevant examples just amounts to the two unrelated sides. But some "gap" Bongard Problems are not "allsorted", since there are more related classes of examples than the two shown, left unsorted.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of examples is partitioned without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of relevant examples for a BP is not clearly delineated anywhere.

The solution to an "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can often be labelled "allsorted", since the pool of all relevant examples just amounts to the two unrelated sides. But some "gap" Bongard Problems are not "allsorted", since there are more related classes of examples than the two shown, left unsorted.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of examples is partitioned without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of relevant examples for a BP is not clearly delineated anywhere.

The solution to an "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can be labelled "allsorted" when the pool of relevant examples just amounts to both the disjoint sides. But a "gap" Bongard Problems is not "allsorted" when there are more related classes of examples than the two shown, left unsorted.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of examples is partitioned without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of relevant examples for a BP is not clearly delineated anywhere.

The solution to an "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can usually be labelled "allsorted": the pool of relevant examples is just both the disjoint sides. Still, a "gap" Bongard Problem might not be "allsorted" if there were other related classes of examples left unsorted.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of relevant examples for a BP is not clearly delineated anywhere.

The solution to an "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can usually be labelled "allsorted": the pool of relevant examples is just both the disjoint sides. Still, a "gap" Bongard Problem might not be "allsorted" if there were other related classes of examples left unsorted.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of relevant examples for a BP is not clearly delineated anywhere.

The solution to a "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can usually be labelled "allsorted": the pool of relevant examples is just both the disjoint sides. Still, a "gap" Bongard Problem might not be "allsorted" if there were other related classes of examples left unsorted.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of possible examples for a typical BP is not clearly delineated.

The solution to a "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can usually be labelled "allsorted": the pool of relevant examples is just both the disjoint sides. Still, a "gap" Bongard Problem might not be "allsorted" if there were other related classes of examples left unsorted.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of possible examples for a typical BP is not clearly delineated.

The solution to a "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can usually be labelled "allsorted": the pool of relevant examples will just be both the disjoint sides. Still, a "gap" Bongard Problem might not be "allsorted" if there were other related classes of examples left unsorted.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of possible examples for a typical BP is not clearly delineated.

The solution to a "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that there is no middle ground between them (keyword "gap" right-BP964) can usually be labelled "allsorted": the pool of relevant examples will just be both the disjoint sides. Still, a "gap" Bongard Problem might not be "allsorted" if there were other related classes of examples left unsorted by the "gap" Problem.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of possible examples for a typical BP is not clearly delineated.

The solution to a "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that they seem unrelated (keyword "gap" right-BP964) can be labelled "allsorted": the pool of relevant examples is just both the disjoint sides.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of examples is partitioned unambiguously and without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of possible examples for a typical BP is not clearly delineated.

The solution to a "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that they seem unrelated (keyword "gap" right-BP964) can be labelled "allsorted": the pool of relevant examples is intuitively just both the disjoint sides.

Left examples have the keyword "allsorted" on the OEBP.

A Bongard Problem is labelled "allsorted" when its pool of examples is partitioned without exception into two groups.

Similarly to the "exact" and "fuzzy" keywords (BP508), calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The space of possible examples for a typical BP is not clearly delineated.

The solution to a "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions).

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that they seem unrelated (keyword "gap" right-BP964) can be labelled "allsorted": the pool of relevant examples is intuitively just both the disjoint sides.

Left examples have the keyword "allsorted" on the OEBP.

A BP is labelled "allsorted" when a pool of examples is partitioned by the BP without exception into two groups.

Similar to the "exact" and "fuzzy" keywords (BP508), "allsorted" is an intuitive judgment. The space of possible examples for a typical BP is not clearly delineated.

The solution to a "allsorted" BP can usually be re-phrased as "___ vs. not so" (see the keyword "notso" left-BP867 for examples of such solutions), although that phrasing may not seem natural.

On the other hand, not every "___ vs. not so" BP should be labelled "allsorted": there could be ambiguous border cases to the rule.

Problems in which the two sides are so different that they seem unrelated (keyword "gap" right-BP964) can be labelled "allsorted": the pool of relevant examples is intuitively just both the disjoint sides.