Search: +meta:BP534
|
|
BP234 |
| Circle falls by gravity on the right of all other objects if let loose vs. circle falls by gravity on the left of all other objects if let loose. |
|
| |
|
|
CROSSREFS
|
Adjacent-numbered pages:
BP229 BP230 BP231 BP232 BP233  *  BP235 BP236 BP237 BP238 BP239
|
|
KEYWORD
|
dual, handed, leftright, physics, orderedtriplet, traditional
|
|
CONCEPT
|
bounding_box (info | search), downward_upward (info | search), left_right (info | search), line_absolute_direction (info | search), absolute_direction (info | search), imagined_motion (info | search), motion (info | search), direction (info | search), gravity (info | search)
|
|
AUTHOR
|
Peter Shanahan
|
|
|
|
|
BP278 |
| Shorter on the left, taller on the right vs. taller on the left, shorter on the right. |
|
| |
|
|
|
|
|
BP279 |
| The left part has more pixels (area) than the right part vs. the left part has fewer pixels than the right part. |
|
| |
|
|
|
|
|
BP286 |
| Decreasing in size from top to bottom vs. increasing in size from top to bottom. |
|
| |
|
|
|
|
|
BP313 |
| Closed curves clockwise, open curves counterclockwise vs. closed curves counterclockwise, open curves clockwise. |
|
| |
|
|
|
|
|
BP337 |
| Black is below upward slopes vs. black is below downward slopes. |
|
| |
|
|
|
|
|
BP357 |
| Decelerating change in quantity, left-to-right vs. accelerating change in quantity, left-to-right. |
|
| |
|
|
|
|
|
BP363 |
| Counterclockwise along the curve following the arrow vs. clockwise along the curve following the arrow. |
|
| |
|
|
|
|
|
BP372 |
| Shape below fits on the left vs. shape below fits on the right. |
|
| |
|
|
COMMENTS
|
See BP805 for the version of this with box-based BPs. |
|
CROSSREFS
|
Adjacent-numbered pages:
BP367 BP368 BP369 BP370 BP371  *  BP373 BP374 BP375 BP376 BP377
|
|
KEYWORD
|
nice, dual, handed, leftright, creativeexamples, structure, traditional, rules
|
|
CONCEPT
|
bongard_problem (info | search), categorization (info | search), feature_cluster (info | search), cluster (info | search), choice (info | search)
|
|
WORLD
|
bdimage_shapes_extra_below_clear_sort [smaller | same | bigger]
|
|
AUTHOR
|
Aaron David Fairbanks
|
|
|
|
|
BP513 |
| Bongard Problems whose left examples could stand alone vs. the right side is necessary to communicate what the left side is. |
|
| |
|
|
COMMENTS
|
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 Bongard Problem can be narrow, e.g. BP6.
Even a rule and its conceptual opposite can be narrow, e.g. BP20.
A Bongard Problem such that one side is narrow and the other side is the non-narrow opposite reads as the narrow side being a subset of the other. See BP881.
What seems like a typical example depends on expectations. (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".) See the keyword stable.
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). |
|
CROSSREFS
|
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
|
|
KEYWORD
|
dual, meta (see left/right), links, keyword, side
|
|
WORLD
|
bp [smaller | same | bigger]
|
|
AUTHOR
|
Aaron David Fairbanks
|
|
|
|
Welcome |
Solve |
Browse |
Lookup |
Recent |
Links |
Register |
Contact
Contribute |
Keywords |
Concepts |
Worlds |
Ambiguities |
Transformations |
Invalid Problems |
Style Guide |
Goals |
Glossary
|
|
|
|
|
|
|
|
|
|