login
Hints
(Greetings from The On-Line Encyclopedia of Bongard Problems!)
Search: ex:BP1266
Displaying 1-5 of 5 results found.     page 1
     Sort: id      Format: long      Filter: (all | no meta | meta)      Mode: (words | no words)
BP509 Bongard Problems that sort all relevant examples vs. Bongard Problems that would leave some unsorted.
BP1
BP3
BP31
BP103
BP312
BP321
BP322
BP329
BP334
BP376
BP384
BP386
BP389
BP390
BP527
BP557
BP559
BP560
BP564
BP569
BP576
BP788
BP820
BP856
BP863
BP891
BP897
BP898
BP905
BP922
BP934
BP935
BP937
BP945
BP949

. . .

BP292
BP508
BP509
BP961
BP1073
BP1208
(edit; present; nest [left/right]; search; history)
COMMENTS

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


A Bongard Problem is labelled "allsorted" when the type of thing it sorts is partitioned unambiguously and without exception into two groups.


Similarly to using the precise and fuzzy keywords, calling a Bongard Problem "allsorted" is a subjective/intuitive judgment. The collection of all relevant potential examples is not clearly delineated anywhere.

(Sometimes it's ambiguous whether to consider certain examples that are ambiguously sorted relevant.)


The solution to an "allsorted" Bongard Problem can usually be re-phrased as "___ vs. not so" (see the keyword notso).

But not every "___ vs. not so" Bongard Problem should be labelled "allsorted"; there could be ambiguous border cases in a "___ vs. not so" Bongard Problem.


Bongard Problems in which the two sides are so different that there is no middle ground between them (keyword gap) are sometimes still labelled "allsorted", since the intuitive pool of all relevant examples just amounts to the two unrelated sides. But some "gap" Bongard Problems are not like that; for example sometimes there are more related classes of examples besides the two shown.


Sometimes the class of all examples in a Bongard Problem is imprecise, but, despite that, the rule sorting those examples is precise. Say, for some potential new example, it is unclear whether it should be included in the Bongard Problem at all, but, if it were included, it would be clear where it should be sorted. A Bongard Problem like this can still be tagged "allsorted".

On the other hand, sometimes the class of all examples is very clear, with an obvious boundary. (Keyword preciseworld.)



In deciding where to sort an example, we think about it until we come to a conclusion; an example isn't here considered ambiguous just because someone might have a hard time with it (keyword hardsort).

However, sometimes the way a Bongard Problem would sort certain examples is an unsolved problem in mathematics, and it may be unknown whether there is even a solution. Whether or not such a Bongard Problem should be labelled "allsorted" might be debated.

(See the keyword proofsrequired.)

One way to resolve this ambiguity is to redefine "allsorted" as meaning that once people decide where an example belongs, it will be on one of the two sides, and they will all agree about it.



There is a distinction to be made between a non-"allsorted" Bongard Problem that could be made "allsorted" by making (finitely many) more examples sorted (thereby modifying or clarifying the solution of the Bongard Problem) and one such that this is not possible while maintaining a comparably simple solution. The former kind would often be labelled precise, in particular when these border cases have been explicitly forbidden from being sorted in the Bongard Problem's definition.

For instance, discrete Bongard Problems that are not allsorted usually fall into the former category.

CROSSREFS

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

"Allsorted" implies precise.

"Allsorted" and both are mutually exclusive.

"Allsorted" and neither are mutually exclusive.

Adjacent-numbered pages:
BP504 BP505 BP506 BP507 BP508  *  BP510 BP511 BP512 BP513 BP514

KEYWORD

fuzzy, meta (see left/right), links, keyword, right-self, sideless, right-it, feedback

WORLD

bp [smaller | same | bigger]

AUTHOR

Aaron David Fairbanks

BP550 Experimental Bongard Problems vs. traditional-style Bongard Problems.
BP195
BP200
BP300
BP359
BP538
BP544
BP545
BP548
BP555
BP570
BP793
BP795
BP797
BP801
BP812
BP813
BP844
BP854
BP859
BP862
BP868
BP902
BP911
BP915
BP920
BP939
BP941
BP942
BP953
BP955
BP957
BP959
BP1008
BP1056
BP1073

. . .

BP1
BP2
BP3
BP4
BP5
BP6
BP7
BP8
BP9
BP10
BP11
BP12
BP13
BP14
BP15
BP16
BP17
BP18
BP19
BP20
BP21
BP22
BP23
BP24
BP25
BP26
BP27
BP28
BP29
BP30
BP31
BP32
BP33
BP34
BP35

. . .

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

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

Right examples have the keyword "traditional" on the OEBP.


Experimental BPs push the boundaries of what makes Bongard Problems Bongard Problems.


Traditional BPs show some simple property of black and white pictures. The OEBP is a place with many wild and absurd Bongard Problems, so it is useful to have an easy way to just find the regular old Bongard Problems.

CROSSREFS

Adjacent-numbered pages:
BP545 BP546 BP547 BP548 BP549  *  BP551 BP552 BP553 BP554 BP555

KEYWORD

subjective, meta (see left/right), links, keyword, left-it

WORLD

bp [smaller | same | bigger]

AUTHOR

Aaron David Fairbanks

BP587 Bongard Problem with solution relating to concept: angle vs. Bongard Problem unrelated to this concept.
BP17
BP32
BP33
BP77
BP262
BP328
BP329
BP354
BP1266
(edit; present; nest [left/right]; search; history)
CROSSREFS

Adjacent-numbered pages:
BP582 BP583 BP584 BP585 BP586  *  BP588 BP589 BP590 BP591 BP592

KEYWORD

meta (see left/right), links, metaconcept, primitive

CONCEPT This MBP is about BPs that feature concept: "angle"

WORLD

bp [smaller | same | bigger]

AUTHOR

Harry E. Foundalis

BP592 Bongard Problem with solution relating to concept: becoming larger / becoming smaller vs. Bongard Problem unrelated to this concept.
BP43
BP74
BP108
BP179
BP180
BP278
BP286
BP300
BP318
BP341
BP350
BP351
BP352
BP357
BP365
BP1266
(edit; present; nest [left/right]; search; history)
CROSSREFS

Adjacent-numbered pages:
BP587 BP588 BP589 BP590 BP591  *  BP593 BP594 BP595 BP596 BP597

KEYWORD

meta (see left/right), links, metaconcept, primitive

CONCEPT This MBP is about BPs that feature concept: "size_increase_decrease"
Searchable synonyms: "larger, becoming", "smaller, becoming", "increasing", "decreasing".

WORLD

bp [smaller | same | bigger]

AUTHOR

Harry E. Foundalis

BP867 Bongard Problem with solution that can be naturally expressed as "___ vs. not so" vs. not so.
BP32
BP77
BP82
BP127
BP243
BP257
BP274
BP288
BP323
BP344
BP376
BP381
BP385
BP390
BP506
BP507
BP515
BP516
BP538
BP541
BP542
BP544
BP545
BP553
BP559
BP569
BP576
BP812
BP816
BP818
BP823
BP825
BP852
BP866
BP867

. . .

BP6

Qat

blimp

notso

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

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

CROSSREFS

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

KEYWORD

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

WORLD

everything [smaller | same]
zoom in left

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