Left-sorted Bongard Problems have the keyword "stub" on the OEBP.

Right-sorted Bongard Problems have the keyword "finished" on the OEBP.

Users are not able to add or remove examples from Problems tagged "finished." (This is unusual; most Bongard Problems on the OEBP can be expanded indefinitely by users.)

A "finished" Bongard Problem will always admit the alternate, convoluted solution "is [left example 1] OR is [left example 2] OR . . . OR is [last left example] vs. is [right example 1] OR is [right example 2] OR . . . OR is [last right example]".

Bongard's original Problems are tagged "finished."

Adjacent-numbered pages:
BP499 BP500 BP501 BP502 BP503  *  BP505 BP506 BP507 BP508 BP509

meta (see left/right), links, keyword, oebp, presentationmatters, left-finite, right-finite, instruction

bppage [smaller | same | bigger]

Aaron David Fairbanks

Left-sorted Bongard Problems have the the keyword "left-narrow" on the OEBP.

Call a rule "narrow" if it is likely to be noticed in a large collection of examples, without any counterexamples provided.

A collection of triangles will be recognized as such; "triangles" is a narrow rule. A collection of non-triangular shapes will just be seen as "shapes"; "not triangles" is not narrow.

Intuitively, a narrow rule seems small in comparison to the space of other related possibilities. Narrow rules tend to be phrased positively ("is [property]"), while non-narrow rules opposite narrow rules tend to be phrased negatively ("is not [property]").

Both sides of a BP can be narrow, e.g. BP6.

Even a rule and its conceptual opposite can be narrow, e.g. BP20.

What seems like a typical example depends on expectations. If one is expecting there to be triangles, the absence of triangles will be noticeable. (See the keyword assumesfamiliarity for Bongard Problems that require the solver to go in with special expectations.)

A person might notice the absence of triangles in a collection of just polygons, because a triangle is such a typical example of a polygon. On the other hand, a person will probably not notice the absence of 174-gons in a collection of polygons.

Typically, any example fitting a narrow rule can be changed slightly to no longer fit. (This is not always the case, however. Consider the narrow rule "is approximately a triangle".)

It is possible for a rule to be "narrow" (communicable by a properly chosen collection of examples) but not clearly communicated by a particular collection of examples satisfying it, e.g., a collection of examples that is too small to communicate it.

Note that this is not just BP514 (right-narrow) flipped.

Is it possible for a rule to be such that some collections of examples do bring it to mind, but no collection of examples unambiguously communicates it as the intended rule? Perhaps there is some border case the rule excludes, but it is not clear whether the border case was intentionally left out. The border case's absence would likely become more conspicuous with more examples (assuming the collection of examples naturally brings this border case to mind).

See BP830 for a version with pictures of Bongard Problems (miniproblems) instead of links.

Adjacent-numbered pages:
BP508 BP509 BP510 BP511 BP512  *  BP514 BP515 BP516 BP517 BP518

dual, meta (see left/right), links, keyword, side

bp [smaller | same | bigger]

Aaron David Fairbanks

Left-sorted BPs have the keyword "left-finite" in the OEBP.

How to distinguish between different examples depends on the Bongard Problem. For example, in BPs about little black dots, examples may be considered the same when they have the same number of dots in all the same positions.

Note that this is not just BP516 (right-finite) flipped.

"Left-finite" implies left-narrow.

See left-listable, which is about an infinite left side that can be organized into a neverending list versus infinite left side that cannot be organized into a neverending list.

"Left-finite" BPs are typically precise.

See BP1032 for a version that sorts images of Bongard Problems (miniproblems) instead of links, and which only sorts images of Bongard Problems about numbers.

Adjacent-numbered pages:
BP510 BP511 BP512 BP513 BP514  *  BP516 BP517 BP518 BP519 BP520

notso, dual, meta (see left/right), links, keyword, side

bp [smaller | same | bigger]
zoom in right (bp_infinite_left_examples)

Aaron David Fairbanks

Left-sorted BPs have the keyword "left-null" on the OEBP.

Right-sorted BPs have the keyword "right-null" on the OEBP.

See BP796 for the version with pictures of Bongard Problems (miniproblems) instead of links to pages on the OEBP.

See BP1160 for the version about an all-black panel instead of all-white.

Adjacent-numbered pages:
BP562 BP563 BP564 BP565 BP566  *  BP568 BP569 BP570 BP571 BP572

meta (see left/right), links, keyword, wellfounded

visualbp [smaller | same | bigger]

Aaron David Fairbanks

Left-sorted BPs have the keyword "left-full" on the OEBP.

For meta-BPs about solution ideas, left-full only means the BP page hopes to include all fitting BP pages on the OEBP (as opposed to all possible Bongard Problems).

As with applying the keywords left-finite and right-finite, deciding what should count as "different" examples depends on the Bongard Problem.

Note this is not just BP574 (right-full) flipped.

TODO: Maybe this should be changed into two keywords: one for non-meta-BPs and one for meta-BPs. - Aaron David Fairbanks, Feb 11 2021

For non-meta BPs, left-full implies left-finite (at least until the OEBP implements a feature that allows algorithmic generation of infinite examples).

Adjacent-numbered pages:
BP568 BP569 BP570 BP571 BP572  *  BP574 BP575 BP576 BP577 BP578

meta (see left/right), links, keyword

bppage [smaller | same | bigger]

Aaron David Fairbanks

Adjacent-numbered pages:
BP694 BP695 BP696 BP697 BP698  *  BP700 BP701 BP702 BP703 BP704

meta (see left/right), links, metaconcept

bp [smaller | same | bigger]

Harry E. Foundalis

Left-sorted BPs have the keyword "notso" on the OEBP.

This meta Bongard Problem is about Bongard Problems featuring two rules that are conceptual opposites.

Sometimes both sides could be seen as the "not" side: consider, for example, two definitions of the same Bongard Problem, "shape has hole vs. does not" and "shape is not filled vs. is". It is possible (albeit perhaps unnatural) to phrase the solution either way when the left and right sides partition all possible relevant examples cleanly into two groups (see the allsorted keyword).

When one property is "positive-seeming" and its opposite is "negative-seeming", it usually means the positive property would be recognized without counter-examples (e.g. a collection of triangles will be seen as such), while the negative property wouldn't be recognized without counter-examples (e.g. a collection of "non-triangle shapes" will just be interpreted as "shapes" unless triangles are shown opposite them).

BP513 (keyword left-narrow) is about Bongard Problems whose left side can be recognized without the right side. When a Bongard Problem is left-narrow and not "right-narrow that usually makes the property on the left seem positive and the property on the right seem negative.

The OEBP by convention has preferred the "positive-seeming" property (when there is one) to be on the left side.

All in all, the keyword "notso" should mean:

1) If the Bongard Problem is "narrow" on at least one side, then it is left-narrow.

2) The right side is the conceptual negation of the left side.

If a Bongard Problem's solution is "[Property A] vs. not so", the "not so" side is everything without [Property A] within some suitable context. A Bongard Problem "triangles vs. not so" might only include simple shapes as non-triangles; it need not include images of boats as non-triangles. It is not necessary for all the kitchen sink to be thrown on the "not so" side (although it is here).

See BP1001 for a version sorting pictures of Bongard Problems (miniproblems) instead of links to pages on the OEBP. (This version is a little different. In BP1001, the kitchen sink of all other possible images is always included on the right "not so" side, rather than a context-dependent conceptual negation.)

Contrast keyword viceversa.

"[Property A] vs. not so" Bongard Problems are often allsorted, meaning they sort all relevant examples--but not always, because sometimes there exist ambiguous border cases, unclear whether they fit [Property A] or not.

Adjacent-numbered pages:
BP862 BP863 BP864 BP865 BP866  *  BP868 BP869 BP870 BP871 BP872

notso, meta (see left/right), links, keyword, left-self, funny

everything [smaller | same]
zoom in left

Aaron David Fairbanks

Left-sorted Bongard Problems have the keyword "unstableworld" on the OEBP.

Right-sorted Bongard Problems have the keyword "stableworld" on the OEBP.

In a "stableworld" Bongard Problem, no small change should outright make an example outright no longer fit in with the others in the Bongard Problem. It is allowed for a small change to make an example slightly less like all the others.

The meaning of "stableworld" is close to "examples have no particular format at all", but not quite the same.

See unstable vs. stable, which is about examples switching sides upon small changes instead of being rendered unsortable.

See BP1144, which is about ALL small changes to ALL examples making them unsortable.

Adjacent-numbered pages:
BP1198 BP1199 BP1200 BP1201 BP1202  *  BP1204 BP1205 BP1206 BP1207 BP1208

meta (see left/right), links, keyword

Aaron David Fairbanks