login
Hints
(Greetings from The On-Line Encyclopedia of Bongard Problems!)
Search: +ex:BP1006
Displaying 1-5 of 5 results found.     page 1
     Sort: id      Format: long      Filter: (all | no meta | meta)      Mode: (words | no words)
BP503 "Nice" Bongard Problems vs. Bongard Problems the OEBP does not need more like.
BP1
BP2
BP3
BP4
BP5
BP6
BP7
BP8
BP9
BP11
BP12
BP15
BP16
BP20
BP23
BP30
BP32
BP33
BP50
BP51
BP57
BP59
BP62
BP70
BP71
BP72
BP74
BP76
BP77
BP85
BP97
BP98
BP100
BP106
BP108

. . .

BP213
BP214
BP221
BP231
BP237
BP262
BP538
BP545
BP548
BP555
BP570
BP801
BP862
BP882
BP915
BP920
BP941
BP1000
BP1008
BP1042
BP1043
BP1129
BP1150
(edit; present; nest [left/right]; search; history)
COMMENTS

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

Right-sorted Bongard Problems have the keyword "less." They are not necessarily "bad," but we do not want more like them.

CROSSREFS

Adjacent-numbered pages:
BP498 BP499 BP500 BP501 BP502  *  BP504 BP505 BP506 BP507 BP508

KEYWORD

subjective, meta (see left/right), links, keyword, oebp, right-finite, left-it, feedback, time

WORLD

bp [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.
BP1
BP31
BP50
BP328
BP334
BP345
BP356
BP373
BP384
BP386
BP559
BP569
BP850
BP856
BP902
BP922
BP932
BP935
BP937
BP988
BP989
BP999
BP1004
BP1005
BP1006
BP1011
BP1049
BP1080
BP1086
BP1093
BP1098
BP1109
BP1110
BP1145
BP1147

. . .

?
BP544
(edit; present; nest [left/right]; search; history)
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

BP687 Bongard Problem with solution relating to concept: recursion vs. Bongard Problem unrelated to this concept.
BP70
BP71
BP167
BP186
BP188
BP322
BP344
BP531
BP532
BP533
BP537
BP538
BP545
BP547
BP794
BP952
BP953
BP954
BP956
BP959
BP961
BP977
BP987
BP992
BP999
BP1002
BP1003
BP1004
BP1005
BP1006
BP1007
BP1019
BP1022
BP1058
BP1059

. . .

(edit; present; nest [left/right]; search; history)
CROSSREFS

Adjacent-numbered pages:
BP682 BP683 BP684 BP685 BP686  *  BP688 BP689 BP690 BP691 BP692

KEYWORD

meta (see left/right), links, metaconcept, primitive, left-it, feedback

CONCEPT This MBP is about BPs that feature concept: "recursion"
Searchable synonyms: "nesting".

WORLD

bp [smaller | same | bigger]

AUTHOR

Harry E. Foundalis

BP691 Bongard Problem with solution relating to concept: self-reference vs. Bongard Problem unrelated to this concept.
BP188
BP344
BP390
BP529
BP530
BP531
BP532
BP533
BP538
BP545
BP818
BP902
BP931
BP953
BP954
BP955
BP957
BP959
BP961
BP987
BP998
BP999
BP1002
BP1003
BP1004
BP1005
BP1006
BP1058
BP1059
BP1060
BP1061
BP1062
BP1063
BP1065
BP1066

. . .

(edit; present; nest [left/right]; search; history)
CROSSREFS

Adjacent-numbered pages:
BP686 BP687 BP688 BP689 BP690  *  BP692 BP693 BP694 BP695 BP696

KEYWORD

meta (see left/right), links, metaconcept, primitive, left-it, feedback

CONCEPT This MBP is about BPs that feature concept: "self-reference"

WORLD

bp [smaller | same | bigger]

AUTHOR

Harry E. Foundalis

BP1158 Bongard Problems in which each example communicates a rule vs. other Bongard Problems.
BP346
BP349
BP350
BP351
BP352
BP353
BP354
BP355
BP356
BP357
BP361
BP362
BP365
BP372
BP379
BP380
BP393
BP792
BP805
BP839
BP841
BP843
BP845
BP846
BP848
BP849
BP852
BP855
BP870
BP893
BP917
BP951
BP973
BP975
BP979

. . .

?
BP347
(edit; present; nest [left/right]; search; history)
COMMENTS

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


In the typical "rules" Bongard Problem, it is possible to come up with many convoluted rules that fit each example, but the intended interpretation is the only simple and obvious one.


Since it is difficult to communicate a rule with little detail, "rules" Bongard Problems are usually infodense.

Typically, each example is itself a bunch of smaller examples that all obey the rule. It is the same as how a Bongard Problems relies on many examples to communicate rules; likely just one example wouldn't get the answer across.

On the other hand, in BP1157 for example, each intended rule is communicated by just one example; these rules have to be particularly simple and intuitive, and the individual examples have to be complicated enough to communicate them.

Often, each rule is communicated by showing several examples of things satisfying it. (See keywords left-narrow and right-narrow.) Contrast Bongard Problems, which are more communicative, by showing some examples satisfying the rule and some examples NOT satisfying the rule.


A "rules" Bongard Problem is often collective. Some examples may admit multiple equally plausible rules, and the correct interpretation of each example only becomes clear once the solution is known. The group of examples together improve the solver's confidence about having understood each individual one right.

It is common that there will be one or two examples with multiple reasonable interpretations due to oversight of the author.

CROSSREFS

All meta Bongard Problems are "rules" Bongard Problems.

Many other Bongard-Problem-like structures seen on the OEBP are also about recognizing a pattern. (See keyword structure.)


"Rules" Bongard Problems are abstract, although the individual rules in them may not be abstract. "Rules" Bongard Problems also usually have the keyword creativeexamples.

Adjacent-numbered pages:
BP1153 BP1154 BP1155 BP1156 BP1157  *  BP1159 BP1160 BP1161 BP1162 BP1163

KEYWORD

fuzzy, meta (see left/right), links, keyword, left-self, rules

AUTHOR

Aaron David Fairbanks

    page 1

Welcome | Solve | Browse | Lookup | Recent | Links | Register | Contact
Contribute | Keywords | Concepts | Worlds | Ambiguities | Transformations | Invalid Problems | Style Guide | Goals | Glossary