How should I create an n-ary relationship?

Question

After reading several articles on n-ary database relationships I'm still in the dark on some aspects of them.

I draw the ER diagram below myself and I purposedly used fake, made-up English words that cannot convey any semantics:

Does it mean that:

1. Each abacot kimes at most once with a gimble, and with many dords and wabes?
2. Similarly, each gimble kimes at most once with an abacot, and with many dords and wabes?
3. Each kiming relationship may include several dords and/or wabes?
4. Will I need three tables to represent this relationship, or one will suffice?

But above all, is it possible to generate a database schema with this diagram alone, without any extra explanations? The database exercises I see in books don't include anything else besides the diagram.

This is how I see it so far:

CREATE TABLE kiming (
    kiming_id INT PRIMARY KEY NOT NULL,
    abacot_id INT NOT NULL REFERENCES abacot (abacot_id),
    gimble_id INT NOT NULL REFERENCES gimble (gimble_id),
    UNIQUE (abacot_id), -- is this necessary?
    UNIQUE (gimble_id)  -- is this necessary?
);

CREATE TABLE kiming_wabe ( -- do I need this table?
    kiming_id INT REFERENCES kiming (kiming_id),
    wabe_id INT REFERENCES wabe (wabe_id)
);

CREATE TABLE kiming_dord ( -- do I need this table?
    kiming_id INT REFERENCES kiming (kiming_id),
    dord_id INT REFERENCES dord (dord_id)
);

Answer 1

To your question of is it possible to generate a database schema with this diagram alone" - the answer is NO.

The diagram is unclear. There is no way to know how the 1's and N's relate to each other. If all I had to go on was the diagram, I could argue for at least 6 different interpretations. The diagram doesn't use a recognizable scheme for representing relationships of this type, so it's all guesswork.

Answer 2

For understanding of you diagram one to one and one to many relationship solution as below. Table schema you will change as required.

CREATE TABLE abacot (
        abacot_id INT PRIMARY KEY NOT NULL,
        abacot_details_columns varchar);

CREATE TABLE gimble (
        gimble_id INT PRIMARY KEY NOT NULL,
        gimble_details_columns varchar);

CREATE TABLE wabe (
        wabe_id INT PRIMARY KEY NOT NULL,
        wabe_details_columns varchar);

CREATE TABLE dord (
        dord_id INT PRIMARY KEY NOT NULL,
        dord_details_columns varchar);

CREATE TABLE kiming (
        kiming_id INT PRIMARY KEY NOT NULL,
        kiming_details_columns varchar 

    CREATE TABLE kiming_relationship_table (
        kiming_id INT PRIMARY KEY NOT NULL,
        abacot_id INT NOT NULL REFERENCES abacot (abacot_id),
        gimble_id INT NOT NULL REFERENCES gimble (gimble_id),
        UNIQUE (abacot_id), -- is this necessary? Yes 
        UNIQUE (gimble_id) , -- is this necessary? Yes 
        wabe_id INT REFERENCES wabe (wabe_id),
        dord_id INT REFERENCES dord (dord_id)
    );