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.

See BP875 for the version with pictures of Bongard Problems instead of links to pages on the OEBP.

Allsorted implies exact (left-BP508).

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" left-BP964) can be labelled "allsorted": the pool of relevant examples is intuitively just both the disjoint sides.

See BP875 for the semi-meta version.

Allsorted implies exact (left-BP508).

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

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

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

The solution to a "wholesort" 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 "wholesort": there could be ambiguous border cases to the rule.

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

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

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

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

The solution to a "wholesort" BP can 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is labelled "wholesort" when some natural pool of examples is partitioned by the BP without exception into two groups.

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

The solution to a "wholesort" BP can 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is labelled "wholesort" when some natural pool of examples is partitioned by the BP without exception into two groups.

The typical BP's space of possible examples has no clear-cur boundaries. Similar to the "exact" and "fuzzy" keywords (BP508), "wholesort" is an intuitive judgment.

The solution to a "wholesort" BP can 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is labelled "wholesort" when some natural pool of examples is partitioned by the BP without exception into two groups. However, the typical BP's space of possible examples has no clear-cur boundaries. Similar to the "exact" and "fuzzy" keywords (BP508), "wholesort" is an intuitive judgment.

The solution to a "wholesort" BP can 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is labelled "wholesort" when some natural pool of examples is partitioned by the BP without exception into two groups. However, the typical BP's space of possible examples has no clear-cur boundaries. Similar to the "exact" and "fuzzy" keywords (BP508), "wholesort" is an intuitive judgment.

A "wholesort" BP's solution can 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is labelled "wholesort" when some natural pool of examples is partitioned by the BP without exception into two groups. However, the typical BP's space of possible examples has no clear-cur boundaries. Similar to the "exact" and "fuzzy" keywords (BP508), "wholesort" is an intuitive judgment.

A "wholesort" BP's solution can be 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is labelled "wholesort" when some natural pool of examples is partitioned by the BP without exception into two groups. However, the typical BP has no clear-cut boundaries on its space of possible examples. Similar to the "exact" and "fuzzy" keywords (BP508), "wholesort" is assigned by intuitive judgment.

A "wholesort" BP's solution can be 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is labelled "wholesort" when some natural pool of examples is partitioned by the BP without exception into two groups. But the typical BP has no clear-cut boundaries on its space of possible examples. Similar to the "exact" and "fuzzy" keywords (BP508), "wholesort" is assigned by intuitive judgment.

A "wholesort" BP's solution can be 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is labelled "wholesort" when some natural pool of examples is partitioned by the BP without exception into two groups. But the typical BP has no clear-cut boundaries on its space of possible examples. Similar to the "exact" and "fuzzy" keywords (BP508), "wholesort" can only be an intuitive judgment.

A "wholesort" BP's solution can be 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is labelled "wholesort" when some natural pool of examples is partitioned by the BP without exception into two groups. Similar to the "exact" and "fuzzy" keywords (BP508), "wholesort" can only be an intuitive characterization agreed upon by the community. The typical BP has no clear-cut boundaries on its space of possible examples.

A "wholesort" BP's solution can be 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is "wholesort" when a natural pool of examples is partitioned by the BP without exception into two groups. Similar to the "exact" and "fuzzy" keywords (BP508), "wholesort" can only be an intuitive characterization agreed upon by the community. The typical BP has no clear-cut boundaries on its space of possible examples.

A "wholesort" BP's solution can be 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is "wholesort" when a natural pool of examples is partitioned by the BP without exception into two groups. Similar to the "exact" and "fuzzy" keywords (BP508), assigning "wholesort" can only be an intuitive judgment agreed upon by the community. The typical BP has no clear-cut boundaries on its space of possible examples.

A "wholesort" BP's solution can be 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is "wholesort" when a natural pool of examples is partitioned by the BP without exception into two groups. Similar to the "exact" and "fuzzy" keywords (BP508), assigning "wholesort" can only be an intuitive judgment, agreed upon by the community. There are no clear-cut boundaries to the space of possible relevant examples.

A "wholesort" BP's solution can be 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 "wholesort": there could be ambiguous border cases.

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

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

A BP is "wholesort" when a natural pool of examples is partitioned by the BP without exception into two groups. Similar to the "exact" and "fuzzy" keywords (BP508), assigning "wholesort" can only be an intuitive judgment, agreed upon by the community. There are no clear-cut boundaries to the space of possible relevant examples for a BP.

A "wholesort" BP's solution can be 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 "wholesort": there could be ambiguous border cases.

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

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

To label a BP "wholesort", one has to intuit an appropriate pool of possible relevant examples, similar to the "exact" and "fuzzy" keywords (BP508). There are no clear-cut boundaries here.

A wholesort BP's solution can be 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 is wholesort: there could be ambiguous border cases.

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