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).

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). - Aaron David Fairbanks, Jun 15 2023

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? Suppose there is a rule such that a collection of examples does bring the intended rule to mind, but it is ambiguous whether this is the intended rule; perhaps there is some border case the rule excludes, and 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). - Aaron David Fairbanks, Jun 15 2023

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 tule? Suppose there is a rule such that a collection of examples does bring the intended rule to mind, but it is ambiguous whether this is the intended rule; perhaps there is some border case the rule excludes, and 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). - Aaron David Fairbanks, Jun 15 2023

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 tule? Suppose there is a rule such that a collection of examples does bring the intended rule to mind, but it is ambiguous whether this is the intended rule; perhaps there is some border case the rule excludes, and 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).

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".)

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

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

Call a pattern "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 pattern. A collection of non-triangular shapes will just be seen as "shapes"; "not triangles" is not narrow.

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

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

Even a pattern 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 pattern can be changed slightly to no longer fit. (This is not always the case, however. Consider the narrow pattern "is approximately a triangle".)

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

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

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

Call a pattern "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 pattern. A collection of non-triangular shapes will just be seen as "shapes"; "not triangles" is not narrow.

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

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

Even a pattern 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 left-BP1111, 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 pattern can be changed slightly to no longer fit. (This is not always the case, however. Consider the narrow pattern "is approximately a triangle".)

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

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

Call a pattern "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 pattern. A collection of non-triangular shapes will just be seen as "shapes"; "not triangles" is not narrow.

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

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

Even a pattern 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 left-BP1111, 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 pattern can be changed slightly to no longer fit. This is not always the case, however. (Consider the narrow pattern "is approximately a triangle".)

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

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

Call a pattern "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 pattern. A collection of non-triangular shapes will just be seen as "shapes"; "not triangles" is not narrow.

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

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

Even a pattern 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 left-BP1111, 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 pattern can be changed slightly to no longer fit.

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