Restaurant / gen1

Your task is to generate a complete and diverse instance, in plain English, for a given category and based on a provided conceptual model description. The instance must adhere to these requirements: - Be self-contained: Include all required attributes, relationships, and related entities in full detail. - Conform to the model: Fulfill the constraints, multiplicities, relationships, and attributes defined in the class diagram model. - Understand the context: Ensure that its attributes and relationships are relevant. - Avoid duplication of instances: Take into consideration those instances previously built to avoid redundancy. - Semantic diversity: From a semantic point of view, incorporate varied scenarios, including regional, linguistic, or cultural differences. - Structural diversity: Include instances with different numbers of elements, different numbers of relationships and complexity, and create varied examples by changing entity attributes.

You are tasked with creating instances of a conceptual model in the UML-based Specification Environment (USE). You will receive: 1. The UML class diagram that the instance follows. 2. A sample syntax of instances creation. 3. A description of the instance that needs to be created.  Your goal is to generate these instances based on the provided description, adhering strictly to these requirements: - The output must be in plain text, with no additional comments, descriptions, or explanations. - Ensure that the created instance adheres to the provided description. - Follow the syntax sample provided, without deviation. - Take into account previously created instances to avoid using duplicate naming.

<role>
You are an expert software and system modeler. You are able to assess the semantic quality of object models that have been created to conform to a domain model. The models are defined in USE (UML-based Specification Environment) and OCL (Object Constraint Language).

Your primary capability is "Semantic Reality Checking". You do not just check for syntactic correctness; you check for real-world plausibility and logical consistency within a given domain.
</role>

<context>
The user will provide two types of content:
1. **Domain Model (.use)**: A class diagram definition including classes, attributes, enums, relationships, multiplicities and roles.
2. **Object Model (.soil)**: An object model. This object model can be seen as a script composed of instructions for the creation of objects, relationships and setting attribute values (snapshot).

Your goal is to act as a judge to determine if the object model represents a **REALISTIC** scenario based on the domain model and common sense real-world logic.
</context>

<definitions>
- **Realistic**: The object model is syntactically correct AND semantically plausible (e.g., A 'Person' has an age between 0 and 120; a 'Car' has a positive price).
- **Unrealistic**: The object model contains contradictions, impossible physical values, or nonsensical relationships (e.g., A 'Person' is their own father; a 'Product' has a negative weight).
- **Doubtful**: You cannot determine whether the object model is realistic or not.
</definitions>

<instructions>
Follow this thinking process strictly before generating the final output:

1. **Analyze the Domain (.use)**: Understand the classes and what they represent in the real world.
2. **Analyze the Instances (.soil)**: Map the created objects to their classes. Look at the specific values assigned to attributes and the relationships created between objects.
3. **Evaluate Semantics**:
    - Apply "Common Sense Knowledge" to the attribute values.
    - Check cardinality and relationship logic beyond simple OCL constraints.
    - Identify any outliers or logical fallacies.
4. **Determine Verdict**: Select one of the defined labels (Realistic/Unrealistic/Doubtful).
</instructions>

<constraints>
- **Tone**: Objective, Analytical, Technical.
- **Verbosity**: Low. Be direct.
- **Reasoning**: The "Why" section must be concise and specific, citing variable names, objects, or relationships when possible.
- Do not output the internal thinking process. Only output the final formatted result.
</constraints>

<output_format>
Structure your response exactly as follows:

**Response**: [Realistic | Unrealistic | Doubtful]
**Why**: [Concise explanation of your reasoning. If Unrealistic, specify the exact objects, values or relationships that break realism.]
</output_format>

<examples>
Example 1:
Input:

<domain_model>
class Person
attributes
    age: Integer
end
class Pet
attributes
    name: String
end
association Ownership between
    Person [1] role owner
    Pet [*] role pets
end
</domain_model>
<object_model>
!new Person('p1')
!p1.age := 250
!new Pet('pet1')
!pet1.name := 'Luna'
… 1.000 more pets creation …
!pet1000.name := 'Max'
!insert (p1, pet1) into Ownership
…1.000 more pets associated with p1 …
!insert (p1, pet1000) into Ownership
</object_model>

Output:

**Response**: Unrealistic
**Why**: The object 'p1' of class 'Person' has an age of 250, which exceeds the biologically plausible lifespan of a human. Although it is not plausible that 1 same person owns 1.000 pets.


Example 2:
Input:

<domain_model>
class Car
attributes
    brand: String
end
class Person
attributes
    name: String
end
association Ownership between
    Person [1] role owner
    Car [*] role cars
end
</domain_model>
<object_model>
!new Person('p1')
!p1.age := 19
!new Car('c1')
!c1.brand := 'Toyota'
!insert (p1, c1) into Ownership
</object_model>

Output:

**Response**: Realistic
**Why**: The object 'c1' has a valid, recognized real-world car brand assigned, and its plausible that a teenager has only one car.


Example 3:
Input:

<domain_model>
class Component
attributes
    setting_val: Integer
    config_mode: String
end
</domain_model>
<object_model>
!new Component('c1')
!c1.setting_val := 8080
!c1.config_mode := 'Legacy'
</object_model>

Output:

**Response**: Doubtful
**Why**: The class 'Component' and attribute 'setting_val' are generic and lack specific real-world semantic context. Without knowing what specific physical or software system this represents, it is impossible to determine if '8080' is a realistic value or an outlier.

</examples>

# Conceptual model description:
## Description
The UML model for a Restaurant system is designed to manage various aspects of a restaurant, including reservations, personnel, menu items, and customer preferences. It outlines the core components necessary for managing restaurant operations, customer interactions, and staff assignments.

### Components
1. **DataTypes**
   - `Date`: Encapsulates date information as a string.
   - `Time`: Encapsulates time information as a string.

2. **Enumerations**
   - `SeatingPreference`: Inside, Patio.
   - `SmokingPreference`: Smoking, NonSmoking.
   - `PaymentMethod`: Cash, CreditCard.
   - `ItemType`: Apetizer, Main, Dessert, Beverage.
   - `UnitOfMeasure`: Ounce, Sheet, Pound, Gram, Dozen.
   - `AllergenType`: Lactose, Seafood, Nuts, Gluten.
   - `Diet`: Vegetarian, Vegan, Kosher, Halal.
   - `Language`: English, Spanish, German, Italian.

3. **Classes**
   - `Restaurant`: Represents the restaurant with attributes like name.
   - `Reservation`: Abstract class for handling reservations; includes time, date, and customer details.
     - `Individual`: Inherits from Reservation; adds seating and smoking preferences.
     - `Banquet`: Inherits from Reservation; includes group specifics and payment options.
   - `Table`: Details about tables such as number, description, and capacity.
   - `ItemOrder`: Tracks time of an order.
   - `MenuItem`: Details about menu items, including description, preparation time, and classification.
   - `FoodItem`: Inventory items with attributes such as unit and purchase flag.
   - `Allergen`: Contains allergen type.
   - `Person`: Base class for individuals associated with the restaurant.
     - `Owner`: Inherits from Person; includes percentage shares.
     - `RegularCustomer`: Inherits from Person; includes preferred language.
   - `DietaryRequirement`: Includes dietary information.
   - `ReportedAllergy`: Records allergen type.
   - `Worker`: Abstract class for restaurant employees with common attributes.
     - `HeadWaiter`, `Waiter`, `Manager`, `Cook`, `Chef`, `BusDriver`: Specialized roles with additional attributes (e.g., languages spoken, experience).

## Relationships
- **Restaurant-Owner (RestaurantOwner):** 
  - Multiplicity: Each Restaurant is associated with 1 or more Owners, and each Owner is associated with 1 or more Restaurants.

- **Restaurant-Reservation (RestaurantReservation):** 
  - Multiplicity: Each Restaurant can have 0 or 1 Reservation, and each Reservation can be associated with 0 or more Restaurants.

- **Reservation-RegularCustomer (ReservationCustomer):**
  - Multiplicity: Each Reservation can have 0 or 1 RegularCustomer, and each RegularCustomer can be associated with 0 or more Reservations.

- **Reservation-Waiter (ReservationWaiter):**
  - Multiplicity: Each Reservation is served by 1 or more Waiters, and each Waiter can serve multiple Reservations.

- **Banquet-BusDriver (BanquetBusDriver):**
  - Multiplicity: Each Banquet is associated with exactly 1 BusDriver, but a BusDriver can be associated with 0 or more Banquets.

- **Reservation-Table (ReservationTable):**
  - Multiplicity: Each Reservation is assigned to 1 or more Tables, and each Table can be assigned to multiple Reservations.

- **Reservation-ItemOrder (ReservationItemOrdered):**
  - Multiplicity: Each Reservation can have 0 or more ItemOrders, and each ItemOrder is associated with exactly 1 Reservation.

- **ItemOrder-MenuItem (ItemOrderMenuItem):**
  - Multiplicity: Each ItemOrder is associated with exactly 1 MenuItem, and each MenuItem can be part of multiple ItemOrders.

- **MenuItem-FoodItem (MenuItemFoodItem):**
  - Multiplicity: Each MenuItem utilizes 0 or more FoodItems, and each FoodItem can be utilized by multiple MenuItems.

- **FoodItem-Allergen (FoodItemAllergen):**
  - Multiplicity: Each FoodItem can contain 0 or more Allergens, and each Allergen can apply to multiple FoodItems.

- **MenuItem-Chef (MenuItemChef):**
  - Multiplicity: Each MenuItem is designed by exactly 1 Chef, and each Chef can design multiple MenuItems.

- **Chef-Cook (ChefCook):**
  - Multiplicity: Each Chef supervises 1 or more Cooks, and each Cook is under the supervision of exactly 1 Chef.

- **HeadWaiter-Waiter (HeadWaiterWaiter):**
  - Multiplicity: Each HeadWaiter is responsible for 1 or more Waiters, and each Waiter is accountable to exactly 1 HeadWaiter.

## Invariants
1. **Table Capacity Constraint (PositiveCapacity):** 
   - Every `Table` must have a capacity greater than 0.

2. **Cook Experience Constraint (PositiveExperience):** 
   - A `Cook`'s years of experience must be greater than or equal to 0.

3. **Owner Shares Constraint (TotalOwnerShares):**
   - The sum of percentage shares held by all `Owners` of a `Restaurant` must equal 100.

4. **Reservation Table Capacity Constraint (TablesCapacityGreaterThanPeople):**
   - The total capacity of tables assigned to a `Reservation` must be greater than or equal to the number of people in that reservation.

# Category: Baseline Instances
Create a baseline instance. This is an instance that represents a realistic typical/standard scenario. Ensure every class and relationship is present in the instance at least once.

Continue with the following description, creating the instance according to the syntax example and this specification: 
### Restaurant Scenario

In one sunny city in southern France, we have "Le Soleil," a popular restaurant renowned for its exquisite cuisine and exceptional service. Let's explore a typical day at this restaurant, involving both individual and banquet reservations, paired with the efficient operation behind the scenes by the restaurant staff.

**Restaurant Instance:**
- **Name:** Le Soleil

**Owner Instance:**
- **Name:** Jacques Dubois
- **Shares:** 60%
- **Language:** French
- **Related Restaurant:** Le Soleil

- **Name:** Marie Martin
- **Shares:** 40%
- **Language:** French
- **Related Restaurant:** Le Soleil

**Table Instances:**
- **Table 1**
  - **Number:** 1
  - **Description:** Near the window, offering a view of the garden.
  - **Capacity:** 4

- **Table 2**
  - **Number:** 2
  - **Description:** Cozy corner table.
  - **Capacity:** 2

- **Table 3**
  - **Number:** 3
  - **Description:** Spacious outdoor table on the patio.
  - **Capacity:** 6

**Regular Customer Instances:**
- **Name:** Giuseppe Rossi
- **Preferred Language:** Italian
- **Reservation Type:** Individual Reservation
- **Seating Preference:** Patio
- **Smoking Preference:** NonSmoking
- Associated with Le Soleil

- **Name:** Anna Thomson
- **Preferred Language:** English
- **Reservation Type:** Banquet Reservation
- Associated with Le Soleil

**Reservation Instances:**
- **Individual Reservation for Giuseppe Rossi**
  - **Date:** 2023-10-15
  - **Time:** 19:00
  - **Seating Preference:** Patio
  - **Smoking Preference:** NonSmoking
  - **Assigned Tables:** Table 3 (Capacity 6)
  - **Associated Waiter:** Sophie Leclerc

- **Banquet Reservation for Anna's Birthday**
  - **Date:** 2023-10-15
  - **Time:** 20:00
  - **Number of People:** 20
  - **Payment Method:** CreditCard
  - **Assigned Tables:** Table 1, Table 2, and Table 3 (Total Capacity 12)
  - **Bus Driver:** Thomas Dupont
  - **Associated Waiters:** Sophie Leclerc and Pierre Monet

**Waiter Instances:**
- **Name:** Sophie Leclerc
- **Languages Spoken:** French, English
- **Experience:** 3 years
- Associated with Le Soleil and both Reservations

- **Name:** Pierre Monet
- **Languages Spoken:** French, Spanish
- **Experience:** 5 years
- Associated with Le Soleil and Banquet Reservation

**Head Waiter Instance:**
- **Name:** Jean-Claude Bernard
- **Languages Spoken:** French, Italian
- **Experience:** 10 years
- **Responsible for:** Sophie Leclerc and Pierre Monet

**Bus Driver Instance:**
- **Name:** Thomas Dupont
- **Experience:** 15 years
- Associated with Anna's Banquet

**Chef Instance:**
- **Name:** Martine Dubois
- **Languages Spoken:** French, English
- **Experience:** 12 years
- **Supervises Cooks:** Alain Lemaire

**Cook Instance:**
- **Name:** Alain Lemaire
- **Languages Spoken:** French
- **Experience:** 4 years
- Supervised by Martine Dubois

**MenuItem Instances:**
- **Ratatouille**
  - **Description:** Classic Provençal stewed vegetable dish.
  - **Preparation Time:** 45 minutes
  - **Classification:** Main
  - **Designed by Chef:** Martine Dubois
  - **Food Items Used:** Eggplant, Zucchini

- **Crème Brûlée**
  - **Description:** Creamy custard topped with a caramelized sugar crust.
  - **Preparation Time:** 20 minutes
  - **Classification:** Dessert
  - **Designed by Chef:** Martine Dubois
  - **Food Items Used:** Cream, Eggs

**FoodItem Instances:**
- **Eggplant**
  - **Unit:** Pound
  - **Purchase:** True
  - **Allergens:** None

- **Zucchini**
  - **Unit:** Pound
  - **Purchase:** True
  - **Allergens:** None

- **Cream**
  - **Unit:** Ounce
  - **Purchase:** True
  - **Allergens:** Lactose

**Allergen Instances:**
- **Lactose**
  - Associated with Food Item: Cream

Through this instance of "Le Soleil," we've captured a detailed snapshot of restaurant operations, customer relations, and the culinary environment, ensuring each class and relationship plays a role in this vibrant culinary experience.

The last output is partially incorrect: 
temp.soil> !waiter7.phoneNumber := '2323232323'            -- Arbitrary phone number
temp.soil> !waiter7.spokenLanguage := #French
<input>:1:0: generation of expression `#French' failed, with following error:

<input>:1:27: Undefined enumeration literal `French'.

temp.soil> !waiter8.phoneNumber := '3434343434'            -- Arbitrary phone number
temp.soil> !waiter8.spokenLanguage := #French
<input>:1:0: generation of expression `#French' failed, with following error:

<input>:1:27: Undefined enumeration literal `French'.

Please provide the complete output corrected

The last output is partially incorrect: 
temp.soil> !waiter8.phoneNumber := '3434343434'            -- Arbitrary phone number
temp.soil> !waiter8.spokenLanguage := #French
<input>:1:0: generation of expression `#French' failed, with following error:

<input>:1:27: Undefined enumeration literal `French'.

Please provide the complete output corrected

The last output is partially incorrect: 
checking structure...
Multiplicity constraint violation in association `ReservationTable':
  Object `table13' of class `Table' is connected to 2 objects of class `Reservation'
  at association end `reservation' but the multiplicity is specified as `1'.
checking invariants...
checking invariant (1) `Cook::PositiveExperience': OK.
checking invariant (2) `Reservation::TablesCapacityGreaterThanPeople': FAILED.
  -> false : Boolean
checking invariant (3) `Restaurant::TotalOwnerShares': OK.
checking invariant (4) `Table::PositiveCapacity': OK.
checked 4 invariants in 0.001s, 1 failure.

Invariants
1. **Table Capacity Constraint (PositiveCapacity):** 
   - Every `Table` must have a capacity greater than 0.

2. **Cook Experience Constraint (PositiveExperience):** 
   - A `Cook`'s years of experience must be greater than or equal to 0.

3. **Owner Shares Constraint (TotalOwnerShares):**
   - The sum of percentage shares held by all `Owners` of a `Restaurant` must equal 100.

4. **Reservation Table Capacity Constraint (TablesCapacityGreaterThanPeople):**
   - The total capacity of tables assigned to a `Reservation` must be greater than or equal to the number of people in that reservation.

Please provide the complete output corrected

The last output is partially incorrect: 
checking invariants...
checking invariant (1) `Cook::PositiveExperience': OK.
checking invariant (2) `Reservation::TablesCapacityGreaterThanPeople': FAILED.
  -> false : Boolean
checking invariant (3) `Restaurant::TotalOwnerShares': OK.
checking invariant (4) `Table::PositiveCapacity': OK.
checked 4 invariants in 0.001s, 1 failure.

Invariants
1. **Table Capacity Constraint (PositiveCapacity):** 
   - Every `Table` must have a capacity greater than 0.

2. **Cook Experience Constraint (PositiveExperience):** 
   - A `Cook`'s years of experience must be greater than or equal to 0.

3. **Owner Shares Constraint (TotalOwnerShares):**
   - The sum of percentage shares held by all `Owners` of a `Restaurant` must equal 100.

4. **Reservation Table Capacity Constraint (TablesCapacityGreaterThanPeople):**
   - The total capacity of tables assigned to a `Reservation` must be greater than or equal to the number of people in that reservation.

Please provide the complete output corrected

<domain_model>
model Restaurant

dataType Date
operations
    Date (date : String)
end

dataType Time
operations
   Time (time : String)
end

enum SeatingPreference {
    Inside,
    Patio
}

enum SmokingPreference {
    Smoking,
    NonSmoking
}

enum PaymentMethod {
    Cash,
    CreditCard
}

enum ItemType {
    Apetizer,
    Main,
    Dessert,
    Beverage
}

enum UnitOfMeasure {
    Ounce,
    Sheet,
    Pound,
    Gram,
    Dozen
}

enum AllergenType {
    Lactose,
    Seafood,
    Nuts,
    Gluten
}

enum Diet {
    Vegetarian,
    Vegan,
    Kosher,
    Halal
}

enum Language {
    English,
    Spanish,
    German,
    Italian
}

class Restaurant
attributes
    name : String
end

abstract class Reservation
attributes
    time : Time
    date : Date
    numberPeople : Integer
    name : String
    phoneNumber : String
    number : Integer
end

class Individual < Reservation
attributes
    seating : SeatingPreference
    smoking : SmokingPreference
end

class Banquet < Reservation
attributes
    groupName : String
    paymentMethod : PaymentMethod
    busService : Boolean
end

class Table
attributes
	number : Integer
    description : String
    capacity : Integer
end

class ItemOrder
attributes
    time : Time
end

class MenuItem
attributes
    description : String
    prepTime : Real
    classification : ItemType
end

class FoodItem
attributes
    number : Integer
    description : String
    purchaseFlag : Boolean
    unit : UnitOfMeasure
end

class Allergen
attributes
    type : AllergenType
end

class Person
attributes
	name : String
end

class Owner < Person
attributes
	percentageShares : Integer
end

class RegularCustomer < Person
attributes
	prefferedLanguage : Language
end

class DietaryRequirement
attributes
	diet : Diet
end

class ReportedAllergy
attributes
	allergen : AllergenType
end

abstract class Worker < Person
attributes
	dateOfBirth : Date
    phoneNumber : String
end

class HeadWaiter < Worker
end

class Waiter < Worker
attributes
    spokenLanguage : Language
end

class Manager < Worker
end

class Cook < Worker
attributes
    yearsOfExperience : Integer
end

class Chef < Worker
end

class BusDriver < Worker
attributes
    driverLicenseNr : String
end


association RestaurantOwner between
    Restaurant [1..*]
    Owner [1..*]
end

association RestaurantReservation between
    Restaurant [0..1]
    Reservation [0..*]
end

association ReservationCustomer between
    Reservation [0..*]
    RegularCustomer [0..1]
end

association ReservationWaiter between
    Reservation [*]
    Waiter [1..*] role servedBy
 end

association BanquetBusDriver between
    Banquet [1]
    BusDriver [0..*]
end

association ReservationTable between
    Reservation [1]
    Table [1..*] role assignedTo
end

association ReservationItemOrdered between
    Reservation [1]
    ItemOrder [0..*]
end

association ItemOrderMenuItem between
    ItemOrder [*]
    MenuItem [1] role item
end

association MenuItemFoodItem between
    MenuItem [*] role isUtilized
    FoodItem [*] role utilizes
end

association FoodItemAllergen between
    FoodItem [*]
    Allergen [*] role contains
end

association MenuItemChef between
    MenuItem [*] role designs
    Chef [1] role designedBy
end

association ChefCook between
    Chef [1] role underSupervisionOf
    Cook [1..*] role supervises
end

association HeadWaiterWaiter between
    HeadWaiter [1]
    Waiter [1..*] role responsibleFor
end


constraints
context Table inv PositiveCapacity:
    self.capacity > 0

context Cook inv PositiveExperience:
    self.yearsOfExperience >= 0

context Restaurant inv TotalOwnerShares:
    self.owner -> collect(o | o.percentageShares) -> sum() = 100

context Reservation inv TablesCapacityGreaterThanPeople:
    self.assignedTo -> collect(t | t.capacity) -> sum() >= self.numberPeople
</domain_model>

<object_model>
!new Restaurant('restaurant5')
!restaurant5.name := 'Le Soleil'

!new Owner('owner9')
!owner9.name := 'Jacques Dubois'
!owner9.percentageShares := 60

!new Owner('owner10')
!owner10.name := 'Marie Martin'
!owner10.percentageShares := 40

!insert (restaurant5, owner9) into RestaurantOwner
!insert (restaurant5, owner10) into RestaurantOwner

!new Table('table11')
!table11.number := 1
!table11.description := 'Near the window, offering a view of the garden.'
!table11.capacity := 4

!new Table('table12')
!table12.number := 2
!table12.description := 'Cozy corner table.'
!table12.capacity := 2

!new Table('table13')
!table13.number := 3
!table13.description := 'Spacious outdoor table on the patio.'
!table13.capacity := 6

!new Table('table14')
!table14.number := 4
!table14.description := 'Elegant dining hall table.'
!table14.capacity := 10

!new RegularCustomer('customer3')
!customer3.name := 'Giuseppe Rossi'
!customer3.prefferedLanguage := #Italian

!new RegularCustomer('customer4')
!customer4.name := 'Anna Thomson'
!customer4.prefferedLanguage := #English

!new Individual('individualReservation1')
!individualReservation1.date := Date('2023-10-15')
!individualReservation1.time := Time('19:00')
!individualReservation1.numberPeople := 1
!individualReservation1.name := 'Giuseppe Rossi'
!individualReservation1.phoneNumber := '1212121212'  -- Arbitrary phone number
!individualReservation1.seating := #Patio
!individualReservation1.smoking := #NonSmoking
!individualReservation1.number := 1

!insert (restaurant5, individualReservation1) into RestaurantReservation
!insert (individualReservation1, customer3) into ReservationCustomer
!insert (individualReservation1, table13) into ReservationTable

!new Banquet('banquet4')
!banquet4.date := Date('2023-10-15')
!banquet4.time := Time('20:00')
!banquet4.groupName := 'Anna\'s Birthday'
!banquet4.numberPeople := 20
!banquet4.paymentMethod := #CreditCard

!insert (restaurant5, banquet4) into RestaurantReservation
!insert (banquet4, customer4) into ReservationCustomer
!insert (banquet4, table11) into ReservationTable
!insert (banquet4, table12) into ReservationTable
!insert (banquet4, table13) into ReservationTable
!insert (banquet4, table14) into ReservationTable  -- Ensure sufficient capacity

!new Waiter('waiter7')
!waiter7.name := 'Sophie Leclerc'
!waiter7.dateOfBirth := Date('1990-01-01')      -- Arbitrary date of birth
!waiter7.phoneNumber := '2323232323'            -- Arbitrary phone number
!waiter7.spokenLanguage := #English

!new Waiter('waiter8')
!waiter8.name := 'Pierre Monet'
!waiter8.dateOfBirth := Date('1988-01-01')      -- Arbitrary date of birth
!waiter8.phoneNumber := '3434343434'            -- Arbitrary phone number
!waiter8.spokenLanguage := #French

!insert (individualReservation1, waiter7) into ReservationWaiter
!insert (banquet4, waiter7) into ReservationWaiter
!insert (banquet4, waiter8) into ReservationWaiter

!new HeadWaiter('headwaiter4')
!headwaiter4.name := 'Jean-Claude Bernard'
!headwaiter4.dateOfBirth := Date('1975-01-01')  -- Arbitrary date of birth
!headwaiter4.phoneNumber := '4545454545'        -- Arbitrary phone number

!insert (headwaiter4, waiter7) into HeadWaiterWaiter
!insert (headwaiter4, waiter8) into HeadWaiterWaiter

!new BusDriver('busdriver4')
!busdriver4.name := 'Thomas Dupont'

!insert (banquet4, busdriver4) into BanquetBusDriver

!new Chef('chef6')
!chef6.name := 'Martine Dubois'
!chef6.dateOfBirth := Date('1983-01-01')        -- Arbitrary date of birth
!chef6.phoneNumber := '5656565656'              -- Arbitrary phone number

!new Cook('cook7')
!cook7.name := 'Alain Lemaire'
!cook7.dateOfBirth := Date('1990-01-01')        -- Arbitrary date of birth
!cook7.phoneNumber := '6767676767'              -- Arbitrary phone number
!cook7.yearsOfExperience := 4

!insert (chef6, cook7) into ChefCook

!new MenuItem('menuitem7')
!menuitem7.description := 'Classic Provençal stewed vegetable dish.'
!menuitem7.prepTime := 45.0
!menuitem7.classification := #Main

!insert (menuitem7, chef6) into MenuItemChef

!new FoodItem('fooditem11')
!fooditem11.number := 10
!fooditem11.description := 'Eggplant'
!fooditem11.purchaseFlag := true
!fooditem11.unit := #Pound

!new FoodItem('fooditem12')
!fooditem12.number := 11
!fooditem12.description := 'Zucchini'
!fooditem12.purchaseFlag := true
!fooditem12.unit := #Pound

!insert (menuitem7, fooditem11) into MenuItemFoodItem
!insert (menuitem7, fooditem12) into MenuItemFoodItem

!new MenuItem('menuitem8')
!menuitem8.description := 'Creamy custard topped with a caramelized sugar crust.'
!menuitem8.prepTime := 20.0
!menuitem8.classification := #Dessert

!insert (menuitem8, chef6) into MenuItemChef

!new FoodItem('fooditem13')
!fooditem13.number := 12
!fooditem13.description := 'Cream'
!fooditem13.purchaseFlag := true
!fooditem13.unit := #Ounce

!new FoodItem('fooditem14')
!fooditem14.number := 13
!fooditem14.description := 'Eggs'
!fooditem14.purchaseFlag := true
!fooditem14.unit := #Ounce

!insert (menuitem8, fooditem13) into MenuItemFoodItem
!insert (menuitem8, fooditem14) into MenuItemFoodItem

!new Allergen('allergen6')
!allergen6.type := #Lactose

!insert (fooditem13, allergen6) into FoodItemAllergen
</object_model>

Your task is to generate a complete and diverse instance, in plain English, for a given category and based on a provided conceptual model description. The instance must adhere to these requirements: - Be self-contained: Include all required attributes, relationships, and related entities in full detail. - Conform to the model: Fulfill the constraints, multiplicities, relationships, and attributes defined in the class diagram model. - Understand the context: Ensure that its attributes and relationships are relevant. - Avoid duplication of instances: Take into consideration those instances previously built to avoid redundancy. - Semantic diversity: From a semantic point of view, incorporate varied scenarios, including regional, linguistic, or cultural differences. - Structural diversity: Include instances with different numbers of elements, different numbers of relationships and complexity, and create varied examples by changing entity attributes.

You are tasked with creating instances of a conceptual model in the UML-based Specification Environment (USE). You will receive: 1. The UML class diagram that the instance follows. 2. A sample syntax of instances creation. 3. A description of the instance that needs to be created.  Your goal is to generate these instances based on the provided description, adhering strictly to these requirements: - The output must be in plain text, with no additional comments, descriptions, or explanations. - Ensure that the created instance adheres to the provided description. - Follow the syntax sample provided, without deviation. - Take into account previously created instances to avoid using duplicate naming.

<role>
You are an expert software and system modeler. You are able to assess the semantic quality of object models that have been created to conform to a domain model. The models are defined in USE (UML-based Specification Environment) and OCL (Object Constraint Language).

Your primary capability is "Semantic Reality Checking". You do not just check for syntactic correctness; you check for real-world plausibility and logical consistency within a given domain.
</role>

<context>
The user will provide two types of content:
1. **Domain Model (.use)**: A class diagram definition including classes, attributes, enums, relationships, multiplicities and roles.
2. **Object Model (.soil)**: An object model. This object model can be seen as a script composed of instructions for the creation of objects, relationships and setting attribute values (snapshot).

Your goal is to act as a judge to determine if the object model represents a **REALISTIC** scenario based on the domain model and common sense real-world logic.
</context>

<definitions>
- **Realistic**: The object model is syntactically correct AND semantically plausible (e.g., A 'Person' has an age between 0 and 120; a 'Car' has a positive price).
- **Unrealistic**: The object model contains contradictions, impossible physical values, or nonsensical relationships (e.g., A 'Person' is their own father; a 'Product' has a negative weight).
- **Doubtful**: You cannot determine whether the object model is realistic or not.
</definitions>

<instructions>
Follow this thinking process strictly before generating the final output:

1. **Analyze the Domain (.use)**: Understand the classes and what they represent in the real world.
2. **Analyze the Instances (.soil)**: Map the created objects to their classes. Look at the specific values assigned to attributes and the relationships created between objects.
3. **Evaluate Semantics**:
    - Apply "Common Sense Knowledge" to the attribute values.
    - Check cardinality and relationship logic beyond simple OCL constraints.
    - Identify any outliers or logical fallacies.
4. **Determine Verdict**: Select one of the defined labels (Realistic/Unrealistic/Doubtful).
</instructions>

<constraints>
- **Tone**: Objective, Analytical, Technical.
- **Verbosity**: Low. Be direct.
- **Reasoning**: The "Why" section must be concise and specific, citing variable names, objects, or relationships when possible.
- Do not output the internal thinking process. Only output the final formatted result.
</constraints>

<output_format>
Structure your response exactly as follows:

**Response**: [Realistic | Unrealistic | Doubtful]
**Why**: [Concise explanation of your reasoning. If Unrealistic, specify the exact objects, values or relationships that break realism.]
</output_format>

<examples>
Example 1:
Input:

<domain_model>
class Person
attributes
    age: Integer
end
class Pet
attributes
    name: String
end
association Ownership between
    Person [1] role owner
    Pet [*] role pets
end
</domain_model>
<object_model>
!new Person('p1')
!p1.age := 250
!new Pet('pet1')
!pet1.name := 'Luna'
… 1.000 more pets creation …
!pet1000.name := 'Max'
!insert (p1, pet1) into Ownership
…1.000 more pets associated with p1 …
!insert (p1, pet1000) into Ownership
</object_model>

Output:

**Response**: Unrealistic
**Why**: The object 'p1' of class 'Person' has an age of 250, which exceeds the biologically plausible lifespan of a human. Although it is not plausible that 1 same person owns 1.000 pets.


Example 2:
Input:

<domain_model>
class Car
attributes
    brand: String
end
class Person
attributes
    name: String
end
association Ownership between
    Person [1] role owner
    Car [*] role cars
end
</domain_model>
<object_model>
!new Person('p1')
!p1.age := 19
!new Car('c1')
!c1.brand := 'Toyota'
!insert (p1, c1) into Ownership
</object_model>

Output:

**Response**: Realistic
**Why**: The object 'c1' has a valid, recognized real-world car brand assigned, and its plausible that a teenager has only one car.


Example 3:
Input:

<domain_model>
class Component
attributes
    setting_val: Integer
    config_mode: String
end
</domain_model>
<object_model>
!new Component('c1')
!c1.setting_val := 8080
!c1.config_mode := 'Legacy'
</object_model>

Output:

**Response**: Doubtful
**Why**: The class 'Component' and attribute 'setting_val' are generic and lack specific real-world semantic context. Without knowing what specific physical or software system this represents, it is impossible to determine if '8080' is a realistic value or an outlier.

</examples>

# Conceptual model description:
## Description
The UML model for a Restaurant system is designed to manage various aspects of a restaurant, including reservations, personnel, menu items, and customer preferences. It outlines the core components necessary for managing restaurant operations, customer interactions, and staff assignments.

### Components
1. **DataTypes**
   - `Date`: Encapsulates date information as a string.
   - `Time`: Encapsulates time information as a string.

2. **Enumerations**
   - `SeatingPreference`: Inside, Patio.
   - `SmokingPreference`: Smoking, NonSmoking.
   - `PaymentMethod`: Cash, CreditCard.
   - `ItemType`: Apetizer, Main, Dessert, Beverage.
   - `UnitOfMeasure`: Ounce, Sheet, Pound, Gram, Dozen.
   - `AllergenType`: Lactose, Seafood, Nuts, Gluten.
   - `Diet`: Vegetarian, Vegan, Kosher, Halal.
   - `Language`: English, Spanish, German, Italian.

3. **Classes**
   - `Restaurant`: Represents the restaurant with attributes like name.
   - `Reservation`: Abstract class for handling reservations; includes time, date, and customer details.
     - `Individual`: Inherits from Reservation; adds seating and smoking preferences.
     - `Banquet`: Inherits from Reservation; includes group specifics and payment options.
   - `Table`: Details about tables such as number, description, and capacity.
   - `ItemOrder`: Tracks time of an order.
   - `MenuItem`: Details about menu items, including description, preparation time, and classification.
   - `FoodItem`: Inventory items with attributes such as unit and purchase flag.
   - `Allergen`: Contains allergen type.
   - `Person`: Base class for individuals associated with the restaurant.
     - `Owner`: Inherits from Person; includes percentage shares.
     - `RegularCustomer`: Inherits from Person; includes preferred language.
   - `DietaryRequirement`: Includes dietary information.
   - `ReportedAllergy`: Records allergen type.
   - `Worker`: Abstract class for restaurant employees with common attributes.
     - `HeadWaiter`, `Waiter`, `Manager`, `Cook`, `Chef`, `BusDriver`: Specialized roles with additional attributes (e.g., languages spoken, experience).

## Relationships
- **Restaurant-Owner (RestaurantOwner):** 
  - Multiplicity: Each Restaurant is associated with 1 or more Owners, and each Owner is associated with 1 or more Restaurants.

- **Restaurant-Reservation (RestaurantReservation):** 
  - Multiplicity: Each Restaurant can have 0 or 1 Reservation, and each Reservation can be associated with 0 or more Restaurants.

- **Reservation-RegularCustomer (ReservationCustomer):**
  - Multiplicity: Each Reservation can have 0 or 1 RegularCustomer, and each RegularCustomer can be associated with 0 or more Reservations.

- **Reservation-Waiter (ReservationWaiter):**
  - Multiplicity: Each Reservation is served by 1 or more Waiters, and each Waiter can serve multiple Reservations.

- **Banquet-BusDriver (BanquetBusDriver):**
  - Multiplicity: Each Banquet is associated with exactly 1 BusDriver, but a BusDriver can be associated with 0 or more Banquets.

- **Reservation-Table (ReservationTable):**
  - Multiplicity: Each Reservation is assigned to 1 or more Tables, and each Table can be assigned to multiple Reservations.

- **Reservation-ItemOrder (ReservationItemOrdered):**
  - Multiplicity: Each Reservation can have 0 or more ItemOrders, and each ItemOrder is associated with exactly 1 Reservation.

- **ItemOrder-MenuItem (ItemOrderMenuItem):**
  - Multiplicity: Each ItemOrder is associated with exactly 1 MenuItem, and each MenuItem can be part of multiple ItemOrders.

- **MenuItem-FoodItem (MenuItemFoodItem):**
  - Multiplicity: Each MenuItem utilizes 0 or more FoodItems, and each FoodItem can be utilized by multiple MenuItems.

- **FoodItem-Allergen (FoodItemAllergen):**
  - Multiplicity: Each FoodItem can contain 0 or more Allergens, and each Allergen can apply to multiple FoodItems.

- **MenuItem-Chef (MenuItemChef):**
  - Multiplicity: Each MenuItem is designed by exactly 1 Chef, and each Chef can design multiple MenuItems.

- **Chef-Cook (ChefCook):**
  - Multiplicity: Each Chef supervises 1 or more Cooks, and each Cook is under the supervision of exactly 1 Chef.

- **HeadWaiter-Waiter (HeadWaiterWaiter):**
  - Multiplicity: Each HeadWaiter is responsible for 1 or more Waiters, and each Waiter is accountable to exactly 1 HeadWaiter.

## Invariants
1. **Table Capacity Constraint (PositiveCapacity):** 
   - Every `Table` must have a capacity greater than 0.

2. **Cook Experience Constraint (PositiveExperience):** 
   - A `Cook`'s years of experience must be greater than or equal to 0.

3. **Owner Shares Constraint (TotalOwnerShares):**
   - The sum of percentage shares held by all `Owners` of a `Restaurant` must equal 100.

4. **Reservation Table Capacity Constraint (TablesCapacityGreaterThanPeople):**
   - The total capacity of tables assigned to a `Reservation` must be greater than or equal to the number of people in that reservation.

# Category: Boundary Instances
Create a boundary case instance. This is an instance that focuses on the extreme upper or lower limits of valid input ranges. For example:
- Upper or lower limits of multiplicities.
- For numbers in a range, the minimum and maximum valid values.
- Empty collections when possible, i.e., when they do not violate the semantics of the model or its constraints.

Continue with the following description, creating the instance according to the syntax example and this specification: 
## Boundary Case Instance: Restaurant System

### Restaurant Details
- **Restaurant Name**: "Limit Delights"

### Owners
1. **Owner 1**: 
   - Name: Emma Smith
   - Percentage Shares: 1%
2. **Owner 2**: 
   - Name: Julian Tan
   - Percentage Shares: 99%

### Regular Customers
1. **Regular Customer**:
   - Name: Carlos Lopez
   - Preferred Language: Spanish

### Workers
1. **Head Waiter**: 
   - Name: Greta Müller
   - Years of Experience: 5
   - Languages Spoken: German, English

2. **Waiters**:
   - Name: Luis Fernandez
   - Years of Experience: 2
   - Languages Spoken: English, Spanish
   - Head Waiter: Greta Müller

3. **Chefs**:
   - Name: Marco Ricci
   - Years of Experience: 10
   - Languages Spoken: Italian, English

4. **Cooks**:
   - Name: Anita Bose
   - Years of Experience: 0 (Minimal Experience)

### Tables (All Tables at Minimum Capacity)
1. **Table 1**: 
   - Number: 1
   - Description: "Corner table near the window"
   - Capacity: 1

### Menu Items
1. **Menu Item**: 
   - Name: "Caprese Salad"
   - Description: "A fresh tomato and mozzarella salad."
   - Preparation Time: 10 minutes
   - Classifications: Apetizer
   - Designer: Marco Ricci

### Food Items
1. **Food Item**: 
   - Name: "Mozzarella Cheese"
   - Unit: Pound
   - Purchase Flag: True

### Allergens
1. **Allergen**: 
   - Allergen Type: Lactose

### Reservations
1. **Reservation (Individual)**:
   - Reservation Date: "2023-11-01"
   - Reservation Time: "18:00"
   - Reserved By: Carlos Lopez
   - Seating Preference: Inside
   - Smoking Preference: NonSmoking
   - Serving Waiter: Luis Fernandez
   - Assigned Table: Table 1
   - Number of People: 1 (Boundary at minimum reservation size, meets Table Capacity Constraint)

### Item Orders
1. **Item Order**:
   - Time Ordered: "18:10"
   - Associated Reservation: Individual Reservation made by Carlos Lopez
   - Ordered Menu Item: Caprese Salad

### Relationships
- The restaurant "Limit Delights" is owned by Emma Smith and Julian Tan, with shares summing up to 100%.
- "Limit Delights" currently has reservations assigned to regular customer Carlos Lopez, who is served by waiter Luis Fernandez.
- Head Waiter Greta Müller oversees Luis Fernandez, the language skills of servers cover English, Spanish, and German.
- Chef Marco Ricci designs menu items, supervised cook Anita Bose has the least required experience.
- Table 1 is utilized for a reservation confirming the minimum seating according to the Table Capacity Constraint.
- Menu item "Caprese Salad" includes food item "Mozzarella Cheese", known for containing the allergen Lactose.

This boundary case instance leverages minimum values and relationships as allowed by the model while meeting all defined invariants, such as the Owner Shares Constraint and Table Capacity Constraint.

<domain_model>
model Restaurant

dataType Date
operations
    Date (date : String)
end

dataType Time
operations
   Time (time : String)
end

enum SeatingPreference {
    Inside,
    Patio
}

enum SmokingPreference {
    Smoking,
    NonSmoking
}

enum PaymentMethod {
    Cash,
    CreditCard
}

enum ItemType {
    Apetizer,
    Main,
    Dessert,
    Beverage
}

enum UnitOfMeasure {
    Ounce,
    Sheet,
    Pound,
    Gram,
    Dozen
}

enum AllergenType {
    Lactose,
    Seafood,
    Nuts,
    Gluten
}

enum Diet {
    Vegetarian,
    Vegan,
    Kosher,
    Halal
}

enum Language {
    English,
    Spanish,
    German,
    Italian
}

class Restaurant
attributes
    name : String
end

abstract class Reservation
attributes
    time : Time
    date : Date
    numberPeople : Integer
    name : String
    phoneNumber : String
    number : Integer
end

class Individual < Reservation
attributes
    seating : SeatingPreference
    smoking : SmokingPreference
end

class Banquet < Reservation
attributes
    groupName : String
    paymentMethod : PaymentMethod
    busService : Boolean
end

class Table
attributes
	number : Integer
    description : String
    capacity : Integer
end

class ItemOrder
attributes
    time : Time
end

class MenuItem
attributes
    description : String
    prepTime : Real
    classification : ItemType
end

class FoodItem
attributes
    number : Integer
    description : String
    purchaseFlag : Boolean
    unit : UnitOfMeasure
end

class Allergen
attributes
    type : AllergenType
end

class Person
attributes
	name : String
end

class Owner < Person
attributes
	percentageShares : Integer
end

class RegularCustomer < Person
attributes
	prefferedLanguage : Language
end

class DietaryRequirement
attributes
	diet : Diet
end

class ReportedAllergy
attributes
	allergen : AllergenType
end

abstract class Worker < Person
attributes
	dateOfBirth : Date
    phoneNumber : String
end

class HeadWaiter < Worker
end

class Waiter < Worker
attributes
    spokenLanguage : Language
end

class Manager < Worker
end

class Cook < Worker
attributes
    yearsOfExperience : Integer
end

class Chef < Worker
end

class BusDriver < Worker
attributes
    driverLicenseNr : String
end


association RestaurantOwner between
    Restaurant [1..*]
    Owner [1..*]
end

association RestaurantReservation between
    Restaurant [0..1]
    Reservation [0..*]
end

association ReservationCustomer between
    Reservation [0..*]
    RegularCustomer [0..1]
end

association ReservationWaiter between
    Reservation [*]
    Waiter [1..*] role servedBy
 end

association BanquetBusDriver between
    Banquet [1]
    BusDriver [0..*]
end

association ReservationTable between
    Reservation [1]
    Table [1..*] role assignedTo
end

association ReservationItemOrdered between
    Reservation [1]
    ItemOrder [0..*]
end

association ItemOrderMenuItem between
    ItemOrder [*]
    MenuItem [1] role item
end

association MenuItemFoodItem between
    MenuItem [*] role isUtilized
    FoodItem [*] role utilizes
end

association FoodItemAllergen between
    FoodItem [*]
    Allergen [*] role contains
end

association MenuItemChef between
    MenuItem [*] role designs
    Chef [1] role designedBy
end

association ChefCook between
    Chef [1] role underSupervisionOf
    Cook [1..*] role supervises
end

association HeadWaiterWaiter between
    HeadWaiter [1]
    Waiter [1..*] role responsibleFor
end


constraints
context Table inv PositiveCapacity:
    self.capacity > 0

context Cook inv PositiveExperience:
    self.yearsOfExperience >= 0

context Restaurant inv TotalOwnerShares:
    self.owner -> collect(o | o.percentageShares) -> sum() = 100

context Reservation inv TablesCapacityGreaterThanPeople:
    self.assignedTo -> collect(t | t.capacity) -> sum() >= self.numberPeople
</domain_model>

<object_model>
!new Restaurant('restaurant2')
!restaurant2.name := 'Limit Delights'

!new Owner('owner3')
!owner3.name := 'Emma Smith'
!owner3.percentageShares := 1

!new Owner('owner4')
!owner4.name := 'Julian Tan'
!owner4.percentageShares := 99

!insert (restaurant2, owner3) into RestaurantOwner
!insert (restaurant2, owner4) into RestaurantOwner

!new RegularCustomer('customer1')
!customer1.name := 'Carlos Lopez'
!customer1.prefferedLanguage := #Spanish

!new HeadWaiter('headwaiter1')
!headwaiter1.name := 'Greta Müller'
!headwaiter1.dateOfBirth := Date('1985-01-01')  -- Arbitrary date of birth
!headwaiter1.phoneNumber := '1234567890'        -- Arbitrary phone number

!new Waiter('waiter1')
!waiter1.name := 'Luis Fernandez'
!waiter1.dateOfBirth := Date('1990-01-01')       -- Arbitrary date of birth
!waiter1.phoneNumber := '0987654321'             -- Arbitrary phone number
!waiter1.spokenLanguage := #English

!insert (headwaiter1, waiter1) into HeadWaiterWaiter

!new Chef('chef1')
!chef1.name := 'Marco Ricci'
!chef1.dateOfBirth := Date('1980-01-01')         -- Arbitrary date of birth
!chef1.phoneNumber := '1122334455'               -- Arbitrary phone number

!new Cook('cook1')
!cook1.name := 'Anita Bose'
!cook1.dateOfBirth := Date('1995-01-01')         -- Arbitrary date of birth
!cook1.phoneNumber := '5566778899'               -- Arbitrary phone number
!cook1.yearsOfExperience := 0

!insert (chef1, cook1) into ChefCook

!new Table('table5')
!table5.number := 1
!table5.description := 'Corner table near the window'
!table5.capacity := 1

!new MenuItem('menuitem1')
!menuitem1.description := 'A fresh tomato and mozzarella salad.'
!menuitem1.prepTime := 10.0
!menuitem1.classification := #Apetizer

!insert (menuitem1, chef1) into MenuItemChef

!new FoodItem('fooditem1')
!fooditem1.number := 1
!fooditem1.description := 'Mozzarella Cheese'
!fooditem1.purchaseFlag := true
!fooditem1.unit := #Pound

!insert (menuitem1, fooditem1) into MenuItemFoodItem

!new Allergen('allergen1')
!allergen1.type := #Lactose

!insert (fooditem1, allergen1) into FoodItemAllergen

!new Individual('reservation1')
!reservation1.time := Time('18:00')
!reservation1.date := Date('2023-11-01')
!reservation1.numberPeople := 1
!reservation1.name := 'Carlos Lopez'
!reservation1.phoneNumber := '3344556677'         -- Arbitrary phone number
!reservation1.number := 1
!reservation1.seating := #Inside
!reservation1.smoking := #NonSmoking

!insert (restaurant2, reservation1) into RestaurantReservation
!insert (reservation1, customer1) into ReservationCustomer
!insert (reservation1, waiter1) into ReservationWaiter
!insert (reservation1, table5) into ReservationTable

!new ItemOrder('itemorder1')
!itemorder1.time := Time('18:10')

!insert (reservation1, itemorder1) into ReservationItemOrdered
!insert (itemorder1, menuitem1) into ItemOrderMenuItem
</object_model>

Your task is to generate a complete and diverse instance, in plain English, for a given category and based on a provided conceptual model description. The instance must adhere to these requirements: - Be self-contained: Include all required attributes, relationships, and related entities in full detail. - Conform to the model: Fulfill the constraints, multiplicities, relationships, and attributes defined in the class diagram model. - Understand the context: Ensure that its attributes and relationships are relevant. - Avoid duplication of instances: Take into consideration those instances previously built to avoid redundancy. - Semantic diversity: From a semantic point of view, incorporate varied scenarios, including regional, linguistic, or cultural differences. - Structural diversity: Include instances with different numbers of elements, different numbers of relationships and complexity, and create varied examples by changing entity attributes.

You are tasked with creating instances of a conceptual model in the UML-based Specification Environment (USE). You will receive: 1. The UML class diagram that the instance follows. 2. A sample syntax of instances creation. 3. A description of the instance that needs to be created.  Your goal is to generate these instances based on the provided description, adhering strictly to these requirements: - The output must be in plain text, with no additional comments, descriptions, or explanations. - Ensure that the created instance adheres to the provided description. - Follow the syntax sample provided, without deviation. - Take into account previously created instances to avoid using duplicate naming.

<role>
You are an expert software and system modeler. You are able to assess the semantic quality of object models that have been created to conform to a domain model. The models are defined in USE (UML-based Specification Environment) and OCL (Object Constraint Language).

Your primary capability is "Semantic Reality Checking". You do not just check for syntactic correctness; you check for real-world plausibility and logical consistency within a given domain.
</role>

<context>
The user will provide two types of content:
1. **Domain Model (.use)**: A class diagram definition including classes, attributes, enums, relationships, multiplicities and roles.
2. **Object Model (.soil)**: An object model. This object model can be seen as a script composed of instructions for the creation of objects, relationships and setting attribute values (snapshot).

Your goal is to act as a judge to determine if the object model represents a **REALISTIC** scenario based on the domain model and common sense real-world logic.
</context>

<definitions>
- **Realistic**: The object model is syntactically correct AND semantically plausible (e.g., A 'Person' has an age between 0 and 120; a 'Car' has a positive price).
- **Unrealistic**: The object model contains contradictions, impossible physical values, or nonsensical relationships (e.g., A 'Person' is their own father; a 'Product' has a negative weight).
- **Doubtful**: You cannot determine whether the object model is realistic or not.
</definitions>

<instructions>
Follow this thinking process strictly before generating the final output:

1. **Analyze the Domain (.use)**: Understand the classes and what they represent in the real world.
2. **Analyze the Instances (.soil)**: Map the created objects to their classes. Look at the specific values assigned to attributes and the relationships created between objects.
3. **Evaluate Semantics**:
    - Apply "Common Sense Knowledge" to the attribute values.
    - Check cardinality and relationship logic beyond simple OCL constraints.
    - Identify any outliers or logical fallacies.
4. **Determine Verdict**: Select one of the defined labels (Realistic/Unrealistic/Doubtful).
</instructions>

<constraints>
- **Tone**: Objective, Analytical, Technical.
- **Verbosity**: Low. Be direct.
- **Reasoning**: The "Why" section must be concise and specific, citing variable names, objects, or relationships when possible.
- Do not output the internal thinking process. Only output the final formatted result.
</constraints>

<output_format>
Structure your response exactly as follows:

**Response**: [Realistic | Unrealistic | Doubtful]
**Why**: [Concise explanation of your reasoning. If Unrealistic, specify the exact objects, values or relationships that break realism.]
</output_format>

<examples>
Example 1:
Input:

<domain_model>
class Person
attributes
    age: Integer
end
class Pet
attributes
    name: String
end
association Ownership between
    Person [1] role owner
    Pet [*] role pets
end
</domain_model>
<object_model>
!new Person('p1')
!p1.age := 250
!new Pet('pet1')
!pet1.name := 'Luna'
… 1.000 more pets creation …
!pet1000.name := 'Max'
!insert (p1, pet1) into Ownership
…1.000 more pets associated with p1 …
!insert (p1, pet1000) into Ownership
</object_model>

Output:

**Response**: Unrealistic
**Why**: The object 'p1' of class 'Person' has an age of 250, which exceeds the biologically plausible lifespan of a human. Although it is not plausible that 1 same person owns 1.000 pets.


Example 2:
Input:

<domain_model>
class Car
attributes
    brand: String
end
class Person
attributes
    name: String
end
association Ownership between
    Person [1] role owner
    Car [*] role cars
end
</domain_model>
<object_model>
!new Person('p1')
!p1.age := 19
!new Car('c1')
!c1.brand := 'Toyota'
!insert (p1, c1) into Ownership
</object_model>

Output:

**Response**: Realistic
**Why**: The object 'c1' has a valid, recognized real-world car brand assigned, and its plausible that a teenager has only one car.


Example 3:
Input:

<domain_model>
class Component
attributes
    setting_val: Integer
    config_mode: String
end
</domain_model>
<object_model>
!new Component('c1')
!c1.setting_val := 8080
!c1.config_mode := 'Legacy'
</object_model>

Output:

**Response**: Doubtful
**Why**: The class 'Component' and attribute 'setting_val' are generic and lack specific real-world semantic context. Without knowing what specific physical or software system this represents, it is impossible to determine if '8080' is a realistic value or an outlier.

</examples>

# Conceptual model description:
## Description
The UML model for a Restaurant system is designed to manage various aspects of a restaurant, including reservations, personnel, menu items, and customer preferences. It outlines the core components necessary for managing restaurant operations, customer interactions, and staff assignments.

### Components
1. **DataTypes**
   - `Date`: Encapsulates date information as a string.
   - `Time`: Encapsulates time information as a string.

2. **Enumerations**
   - `SeatingPreference`: Inside, Patio.
   - `SmokingPreference`: Smoking, NonSmoking.
   - `PaymentMethod`: Cash, CreditCard.
   - `ItemType`: Apetizer, Main, Dessert, Beverage.
   - `UnitOfMeasure`: Ounce, Sheet, Pound, Gram, Dozen.
   - `AllergenType`: Lactose, Seafood, Nuts, Gluten.
   - `Diet`: Vegetarian, Vegan, Kosher, Halal.
   - `Language`: English, Spanish, German, Italian.

3. **Classes**
   - `Restaurant`: Represents the restaurant with attributes like name.
   - `Reservation`: Abstract class for handling reservations; includes time, date, and customer details.
     - `Individual`: Inherits from Reservation; adds seating and smoking preferences.
     - `Banquet`: Inherits from Reservation; includes group specifics and payment options.
   - `Table`: Details about tables such as number, description, and capacity.
   - `ItemOrder`: Tracks time of an order.
   - `MenuItem`: Details about menu items, including description, preparation time, and classification.
   - `FoodItem`: Inventory items with attributes such as unit and purchase flag.
   - `Allergen`: Contains allergen type.
   - `Person`: Base class for individuals associated with the restaurant.
     - `Owner`: Inherits from Person; includes percentage shares.
     - `RegularCustomer`: Inherits from Person; includes preferred language.
   - `DietaryRequirement`: Includes dietary information.
   - `ReportedAllergy`: Records allergen type.
   - `Worker`: Abstract class for restaurant employees with common attributes.
     - `HeadWaiter`, `Waiter`, `Manager`, `Cook`, `Chef`, `BusDriver`: Specialized roles with additional attributes (e.g., languages spoken, experience).

## Relationships
- **Restaurant-Owner (RestaurantOwner):** 
  - Multiplicity: Each Restaurant is associated with 1 or more Owners, and each Owner is associated with 1 or more Restaurants.

- **Restaurant-Reservation (RestaurantReservation):** 
  - Multiplicity: Each Restaurant can have 0 or 1 Reservation, and each Reservation can be associated with 0 or more Restaurants.

- **Reservation-RegularCustomer (ReservationCustomer):**
  - Multiplicity: Each Reservation can have 0 or 1 RegularCustomer, and each RegularCustomer can be associated with 0 or more Reservations.

- **Reservation-Waiter (ReservationWaiter):**
  - Multiplicity: Each Reservation is served by 1 or more Waiters, and each Waiter can serve multiple Reservations.

- **Banquet-BusDriver (BanquetBusDriver):**
  - Multiplicity: Each Banquet is associated with exactly 1 BusDriver, but a BusDriver can be associated with 0 or more Banquets.

- **Reservation-Table (ReservationTable):**
  - Multiplicity: Each Reservation is assigned to 1 or more Tables, and each Table can be assigned to multiple Reservations.

- **Reservation-ItemOrder (ReservationItemOrdered):**
  - Multiplicity: Each Reservation can have 0 or more ItemOrders, and each ItemOrder is associated with exactly 1 Reservation.

- **ItemOrder-MenuItem (ItemOrderMenuItem):**
  - Multiplicity: Each ItemOrder is associated with exactly 1 MenuItem, and each MenuItem can be part of multiple ItemOrders.

- **MenuItem-FoodItem (MenuItemFoodItem):**
  - Multiplicity: Each MenuItem utilizes 0 or more FoodItems, and each FoodItem can be utilized by multiple MenuItems.

- **FoodItem-Allergen (FoodItemAllergen):**
  - Multiplicity: Each FoodItem can contain 0 or more Allergens, and each Allergen can apply to multiple FoodItems.

- **MenuItem-Chef (MenuItemChef):**
  - Multiplicity: Each MenuItem is designed by exactly 1 Chef, and each Chef can design multiple MenuItems.

- **Chef-Cook (ChefCook):**
  - Multiplicity: Each Chef supervises 1 or more Cooks, and each Cook is under the supervision of exactly 1 Chef.

- **HeadWaiter-Waiter (HeadWaiterWaiter):**
  - Multiplicity: Each HeadWaiter is responsible for 1 or more Waiters, and each Waiter is accountable to exactly 1 HeadWaiter.

## Invariants
1. **Table Capacity Constraint (PositiveCapacity):** 
   - Every `Table` must have a capacity greater than 0.

2. **Cook Experience Constraint (PositiveExperience):** 
   - A `Cook`'s years of experience must be greater than or equal to 0.

3. **Owner Shares Constraint (TotalOwnerShares):**
   - The sum of percentage shares held by all `Owners` of a `Restaurant` must equal 100.

4. **Reservation Table Capacity Constraint (TablesCapacityGreaterThanPeople):**
   - The total capacity of tables assigned to a `Reservation` must be greater than or equal to the number of people in that reservation.

# Category: Complex Instances
Create a complex instance that is realistic and contains multiple interrelated entities and/or entities that are involved in multiple constraints.

Continue with the following description, creating the instance according to the syntax example and this specification: 
## Complex Instance: Global Cuisine Restaurant

### Restaurant: "Global Bites"
- **Name:** Global Bites
- **Owners:**
  1. **Owner Name:** Anna Leong
     - **Percentage Shares:** 60%
     - **Language Spoken:** English, Mandarin
  2. **Owner Name:** Luis Gonzalez
     - **Percentage Shares:** 40%
     - **Language Spoken:** English, Spanish
- **Menus:**
  1. **Chef:** Giovanni Rossi
     - **Language Spoken:** Italian, English
     - **Cook Team:**
       - **Cook Name:** Maria Elizondo
         - **Years of Experience:** 4
         - **Languages Spoken:** Spanish, English
       - **Cook Name:** Chul Min
         - **Years of Experience:** 3
         - **Languages Spoken:** Korean, English

### Reservations
1. **Reservation (Banquet):**
   - **Date:** October 15, 2023
   - **Time:** 19:30
   - **Group Name:** Tech Innovators - Annual Gala
   - **Payment Method:** CreditCard
   - **Assigned BusDriver:** Gerhard Dietrich
     - **Languages Spoken:** English, German
   - **Assigned Tables:**
     - **Table 1:** 
       - **Number:** 7
       - **Description:** Near the stage
       - **Capacity:** 10
     - **Table 2:** 
       - **Number:** 8
       - **Description:** Next to bar
       - **Capacity:** 8
   - **Total Attendees:** 18
   - **Assigned Waiters:**
     - **HeadWaiter:** Aisha Karim
       - **Languages Spoken:** Arabic, English
     - **Waiters:**
       - **Waiter Name:** Mike Tan
         - **Languages Spoken:** English, Cantonese
       - **Waiter Name:** Sofya Petrova
         - **Languages Spoken:** Russian, English

2. **Reservation (Individual):**
   - **Date:** October 15, 2023
   - **Time:** 20:00
   - **Customer Name:** Sophie Müller
   - **Seating Preference:** Inside
   - **Smoking Preference:** NonSmoking
   - **Assigned Table:** 
     - **Number:** 10
     - **Description:** Window view
     - **Capacity:** 2
   - **Assigned Waiters:**
     - **HeadWaiter:** Same as above
     - **Waiter Name:** Jinan Xu
         - **Languages Spoken:** Mandarin, English

### Menu Items
1. **Menu Item (Dessert): Tiramisu**
   - **Description:** Classic Italian coffee-flavored dessert
   - **Preparation Time:** 15 minutes
   - **Chef:** Giovanni Rossi (as above)
   - **Food Items:**
     - **FoodItem 1:** Espresso
       - **Unit:** Ounce
       - **Purchased:** True
     - **FoodItem 2:** Mascarpone Cheese
       - **Unit:** Gram
       - **Allergens:**
         - **Allergen Type:** Lactose

2. **Menu Item (Main): Biryani**
   - **Description:** Spiced rice with chicken and vegetables
   - **Preparation Time:** 30 minutes
   - **Chef:** Giovanni Rossi (as above)
   - **Food Items:**
     - **FoodItem 1:** Basmati Rice
       - **Unit:** Pound
     - **FoodItem 2:** Chicken
       - **Unit:** Pound
     - **FoodItem 3:** Mixed Vegetables
       - **Unit:** Pound
       - **Dietary Requirements:** Vegetarian
     - **FoodItem 4:** Nuts
       - **Unit:** Ounce
       - **Allergen Type:** Nuts

### Dietary Requirements
- **RegularCustomer:** Sophie Müller
  - **Dietary Requirement:** Vegetarian
  - **Preferred Language:** German

This instance captures complex operations and associations within the restaurant system, highlighting diverse staff roles and customer preferences across different cultural experiences. The structure adheres to the UML model while showcasing real-world restaurant dynamics.

The last output is partially incorrect: 
temp.soil> 
temp.soil> !insert (banquet2, headwaiter2) into ReservationWaiter
<input>:1:0: Participant 2 of association `ReservationWaiter' must be of type `Waiter', but `headwaiter2' is of type `HeadWaiter'.

temp.soil> !insert (headwaiter2, waiter4) into HeadWaiterWaiter
temp.soil> !insert (reservation2, headwaiter2) into ReservationWaiter
<input>:1:0: Participant 2 of association `ReservationWaiter' must be of type `Waiter', but `headwaiter2' is of type `HeadWaiter'.

temp.soil> 
temp.soil> !insert (fooditem6, diet1) into FoodItemAllergen
<input>:1:0: Participant 2 of association `FoodItemAllergen' must be of type `Allergen', but `diet1' is of type `DietaryRequirement'.

temp.soil> 
temp.soil> !insert (customer2, diet2) into DietaryRequirement
<input>:1:0: Association `DietaryRequirement' does not exist.

Please provide the complete output corrected

The last output is partially incorrect: 
temp.soil> 
temp.soil> !insert (fooditem6, diet1) into FoodItemDietaryRequirement
<input>:1:0: Association `FoodItemDietaryRequirement' does not exist.

temp.soil> !new ReportedAllergy('allergy2')
temp.soil> !allergy2.allergen := #Vegetarian
<input>:1:0: Type mismatch in assignment expression. Expected type `AllergenType', found `Diet'.

temp.soil> !insert (reservation2, customer2) into ReservationCustomer
temp.soil> !insert (customer2, allergy2) into ReportedAllergy
<input>:1:0: Association `ReportedAllergy' does not exist.

Please provide the complete output corrected

<domain_model>
model Restaurant

dataType Date
operations
    Date (date : String)
end

dataType Time
operations
   Time (time : String)
end

enum SeatingPreference {
    Inside,
    Patio
}

enum SmokingPreference {
    Smoking,
    NonSmoking
}

enum PaymentMethod {
    Cash,
    CreditCard
}

enum ItemType {
    Apetizer,
    Main,
    Dessert,
    Beverage
}

enum UnitOfMeasure {
    Ounce,
    Sheet,
    Pound,
    Gram,
    Dozen
}

enum AllergenType {
    Lactose,
    Seafood,
    Nuts,
    Gluten
}

enum Diet {
    Vegetarian,
    Vegan,
    Kosher,
    Halal
}

enum Language {
    English,
    Spanish,
    German,
    Italian
}

class Restaurant
attributes
    name : String
end

abstract class Reservation
attributes
    time : Time
    date : Date
    numberPeople : Integer
    name : String
    phoneNumber : String
    number : Integer
end

class Individual < Reservation
attributes
    seating : SeatingPreference
    smoking : SmokingPreference
end

class Banquet < Reservation
attributes
    groupName : String
    paymentMethod : PaymentMethod
    busService : Boolean
end

class Table
attributes
	number : Integer
    description : String
    capacity : Integer
end

class ItemOrder
attributes
    time : Time
end

class MenuItem
attributes
    description : String
    prepTime : Real
    classification : ItemType
end

class FoodItem
attributes
    number : Integer
    description : String
    purchaseFlag : Boolean
    unit : UnitOfMeasure
end

class Allergen
attributes
    type : AllergenType
end

class Person
attributes
	name : String
end

class Owner < Person
attributes
	percentageShares : Integer
end

class RegularCustomer < Person
attributes
	prefferedLanguage : Language
end

class DietaryRequirement
attributes
	diet : Diet
end

class ReportedAllergy
attributes
	allergen : AllergenType
end

abstract class Worker < Person
attributes
	dateOfBirth : Date
    phoneNumber : String
end

class HeadWaiter < Worker
end

class Waiter < Worker
attributes
    spokenLanguage : Language
end

class Manager < Worker
end

class Cook < Worker
attributes
    yearsOfExperience : Integer
end

class Chef < Worker
end

class BusDriver < Worker
attributes
    driverLicenseNr : String
end


association RestaurantOwner between
    Restaurant [1..*]
    Owner [1..*]
end

association RestaurantReservation between
    Restaurant [0..1]
    Reservation [0..*]
end

association ReservationCustomer between
    Reservation [0..*]
    RegularCustomer [0..1]
end

association ReservationWaiter between
    Reservation [*]
    Waiter [1..*] role servedBy
 end

association BanquetBusDriver between
    Banquet [1]
    BusDriver [0..*]
end

association ReservationTable between
    Reservation [1]
    Table [1..*] role assignedTo
end

association ReservationItemOrdered between
    Reservation [1]
    ItemOrder [0..*]
end

association ItemOrderMenuItem between
    ItemOrder [*]
    MenuItem [1] role item
end

association MenuItemFoodItem between
    MenuItem [*] role isUtilized
    FoodItem [*] role utilizes
end

association FoodItemAllergen between
    FoodItem [*]
    Allergen [*] role contains
end

association MenuItemChef between
    MenuItem [*] role designs
    Chef [1] role designedBy
end

association ChefCook between
    Chef [1] role underSupervisionOf
    Cook [1..*] role supervises
end

association HeadWaiterWaiter between
    HeadWaiter [1]
    Waiter [1..*] role responsibleFor
end


constraints
context Table inv PositiveCapacity:
    self.capacity > 0

context Cook inv PositiveExperience:
    self.yearsOfExperience >= 0

context Restaurant inv TotalOwnerShares:
    self.owner -> collect(o | o.percentageShares) -> sum() = 100

context Reservation inv TablesCapacityGreaterThanPeople:
    self.assignedTo -> collect(t | t.capacity) -> sum() >= self.numberPeople
</domain_model>

<object_model>
!new Restaurant('restaurant3')
!restaurant3.name := 'Global Bites'

!new Owner('owner5')
!owner5.name := 'Anna Leong'
!owner5.percentageShares := 60

!new Owner('owner6')
!owner6.name := 'Luis Gonzalez'
!owner6.percentageShares := 40

!insert (restaurant3, owner5) into RestaurantOwner
!insert (restaurant3, owner6) into RestaurantOwner

!new Chef('chef2')
!chef2.name := 'Giovanni Rossi'
!chef2.dateOfBirth := Date('1978-01-01')  -- Arbitrary date of birth
!chef2.phoneNumber := '1010101010'        -- Arbitrary phone number

!new Cook('cook2')
!cook2.name := 'Maria Elizondo'
!cook2.dateOfBirth := Date('1988-01-01')  -- Arbitrary date of birth
!cook2.phoneNumber := '2020202020'        -- Arbitrary phone number
!cook2.yearsOfExperience := 4

!new Cook('cook3')
!cook3.name := 'Chul Min'
!cook3.dateOfBirth := Date('1990-01-01')  -- Arbitrary date of birth
!cook3.phoneNumber := '3030303030'        -- Arbitrary phone number
!cook3.yearsOfExperience := 3

!insert (chef2, cook2) into ChefCook
!insert (chef2, cook3) into ChefCook

!new Banquet('banquet2')
!banquet2.date := Date('2023-10-15')
!banquet2.time := Time('19:30')
!banquet2.groupName := 'Tech Innovators - Annual Gala'
!banquet2.numberPeople := 18
!banquet2.paymentMethod := #CreditCard

!insert (restaurant3, banquet2) into RestaurantReservation

!new BusDriver('busdriver2')
!busdriver2.name := 'Gerhard Dietrich'

!insert (banquet2, busdriver2) into BanquetBusDriver

!new Table('table6')
!table6.number := 7
!table6.description := 'Near the stage'
!table6.capacity := 10

!new Table('table7')
!table7.number := 8
!table7.description := 'Next to bar'
!table7.capacity := 8

!insert (banquet2, table6) into ReservationTable
!insert (banquet2, table7) into ReservationTable

!new HeadWaiter('headwaiter2')
!headwaiter2.name := 'Aisha Karim'
!headwaiter2.dateOfBirth := Date('1980-01-01')  -- Arbitrary date of birth
!headwaiter2.phoneNumber := '4040404040'        -- Arbitrary phone number

!new Waiter('waiter2')
!waiter2.name := 'Mike Tan'
!waiter2.dateOfBirth := Date('1990-01-01')      -- Arbitrary date of birth
!waiter2.phoneNumber := '5050505050'            -- Arbitrary phone number

!new Waiter('waiter3')
!waiter3.name := 'Sofya Petrova'
!waiter3.dateOfBirth := Date('1992-01-01')      -- Arbitrary date of birth
!waiter3.phoneNumber := '6060606060'            -- Arbitrary phone number

!insert (headwaiter2, waiter2) into HeadWaiterWaiter
!insert (headwaiter2, waiter3) into HeadWaiterWaiter

!insert (banquet2, waiter2) into ReservationWaiter
!insert (banquet2, waiter3) into ReservationWaiter

!new Individual('reservation2')
!reservation2.date := Date('2023-10-15')
!reservation2.time := Time('20:00')
!reservation2.name := 'Sophie Müller'
!reservation2.phoneNumber := '7070707070'        -- Arbitrary phone number
!reservation2.number := 2
!reservation2.numberPeople := 2
!reservation2.seating := #Inside
!reservation2.smoking := #NonSmoking

!insert (restaurant3, reservation2) into RestaurantReservation

!new Table('table8')
!table8.number := 10
!table8.description := 'Window view'
!table8.capacity := 2

!insert (reservation2, table8) into ReservationTable

!new Waiter('waiter4')
!waiter4.name := 'Jinan Xu'
!waiter4.dateOfBirth := Date('1991-01-01')      -- Arbitrary date of birth
!waiter4.phoneNumber := '8080808080'            -- Arbitrary phone number

!insert (headwaiter2, waiter4) into HeadWaiterWaiter
!insert (reservation2, waiter4) into ReservationWaiter

!new MenuItem('menuitem2')
!menuitem2.description := 'Classic Italian coffee-flavored dessert'
!menuitem2.prepTime := 15.0
!menuitem2.classification := #Dessert

!insert (menuitem2, chef2) into MenuItemChef

!new FoodItem('fooditem2')
!fooditem2.number := 1
!fooditem2.description := 'Espresso'
!fooditem2.purchaseFlag := true
!fooditem2.unit := #Ounce

!new FoodItem('fooditem3')
!fooditem3.number := 2
!fooditem3.description := 'Mascarpone Cheese'
!fooditem3.unit := #Gram

!insert (menuitem2, fooditem2) into MenuItemFoodItem
!insert (menuitem2, fooditem3) into MenuItemFoodItem

!new Allergen('allergen2')
!allergen2.type := #Lactose

!insert (fooditem3, allergen2) into FoodItemAllergen

!new MenuItem('menuitem3')
!menuitem3.description := 'Spiced rice with chicken and vegetables'
!menuitem3.prepTime := 30.0
!menuitem3.classification := #Main

!insert (menuitem3, chef2) into MenuItemChef

!new FoodItem('fooditem4')
!fooditem4.number := 3
!fooditem4.description := 'Basmati Rice'
!fooditem4.unit := #Pound

!new FoodItem('fooditem5')
!fooditem5.number := 4
!fooditem5.description := 'Chicken'
!fooditem5.unit := #Pound

!new FoodItem('fooditem6')
!fooditem6.number := 5
!fooditem6.description := 'Mixed Vegetables'
!fooditem6.unit := #Pound

!insert (menuitem3, fooditem4) into MenuItemFoodItem
!insert (menuitem3, fooditem5) into MenuItemFoodItem
!insert (menuitem3, fooditem6) into MenuItemFoodItem

!new DietaryRequirement('diet1')
!diet1.diet := #Vegetarian

!insert (fooditem6, diet1) into MenuItemFoodItem

!new FoodItem('fooditem7')
!fooditem7.number := 6
!fooditem7.description := 'Nuts'
!fooditem7.unit := #Ounce

!new Allergen('allergen3')
!allergen3.type := #Nuts

!insert (fooditem7, allergen3) into FoodItemAllergen

!new RegularCustomer('customer2')
!customer2.name := 'Sophie Müller'
!customer2.prefferedLanguage := #German

!insert (reservation2, customer2) into ReservationCustomer
</object_model>

Your task is to generate a complete and diverse instance, in plain English, for a given category and based on a provided conceptual model description. The instance must adhere to these requirements: - Be self-contained: Include all required attributes, relationships, and related entities in full detail. - Conform to the model: Fulfill the constraints, multiplicities, relationships, and attributes defined in the class diagram model. - Understand the context: Ensure that its attributes and relationships are relevant. - Avoid duplication of instances: Take into consideration those instances previously built to avoid redundancy. - Semantic diversity: From a semantic point of view, incorporate varied scenarios, including regional, linguistic, or cultural differences. - Structural diversity: Include instances with different numbers of elements, different numbers of relationships and complexity, and create varied examples by changing entity attributes.

You are tasked with creating instances of a conceptual model in the UML-based Specification Environment (USE). You will receive: 1. The UML class diagram that the instance follows. 2. A sample syntax of instances creation. 3. A description of the instance that needs to be created.  Your goal is to generate these instances based on the provided description, adhering strictly to these requirements: - The output must be in plain text, with no additional comments, descriptions, or explanations. - Ensure that the created instance adheres to the provided description. - Follow the syntax sample provided, without deviation. - Take into account previously created instances to avoid using duplicate naming.

<role>
You are an expert software and system modeler. You are able to assess the semantic quality of object models that have been created to conform to a domain model. The models are defined in USE (UML-based Specification Environment) and OCL (Object Constraint Language).

Your primary capability is "Semantic Reality Checking". You do not just check for syntactic correctness; you check for real-world plausibility and logical consistency within a given domain.
</role>

<context>
The user will provide two types of content:
1. **Domain Model (.use)**: A class diagram definition including classes, attributes, enums, relationships, multiplicities and roles.
2. **Object Model (.soil)**: An object model. This object model can be seen as a script composed of instructions for the creation of objects, relationships and setting attribute values (snapshot).

Your goal is to act as a judge to determine if the object model represents a **REALISTIC** scenario based on the domain model and common sense real-world logic.
</context>

<definitions>
- **Realistic**: The object model is syntactically correct AND semantically plausible (e.g., A 'Person' has an age between 0 and 120; a 'Car' has a positive price).
- **Unrealistic**: The object model contains contradictions, impossible physical values, or nonsensical relationships (e.g., A 'Person' is their own father; a 'Product' has a negative weight).
- **Doubtful**: You cannot determine whether the object model is realistic or not.
</definitions>

<instructions>
Follow this thinking process strictly before generating the final output:

1. **Analyze the Domain (.use)**: Understand the classes and what they represent in the real world.
2. **Analyze the Instances (.soil)**: Map the created objects to their classes. Look at the specific values assigned to attributes and the relationships created between objects.
3. **Evaluate Semantics**:
    - Apply "Common Sense Knowledge" to the attribute values.
    - Check cardinality and relationship logic beyond simple OCL constraints.
    - Identify any outliers or logical fallacies.
4. **Determine Verdict**: Select one of the defined labels (Realistic/Unrealistic/Doubtful).
</instructions>

<constraints>
- **Tone**: Objective, Analytical, Technical.
- **Verbosity**: Low. Be direct.
- **Reasoning**: The "Why" section must be concise and specific, citing variable names, objects, or relationships when possible.
- Do not output the internal thinking process. Only output the final formatted result.
</constraints>

<output_format>
Structure your response exactly as follows:

**Response**: [Realistic | Unrealistic | Doubtful]
**Why**: [Concise explanation of your reasoning. If Unrealistic, specify the exact objects, values or relationships that break realism.]
</output_format>

<examples>
Example 1:
Input:

<domain_model>
class Person
attributes
    age: Integer
end
class Pet
attributes
    name: String
end
association Ownership between
    Person [1] role owner
    Pet [*] role pets
end
</domain_model>
<object_model>
!new Person('p1')
!p1.age := 250
!new Pet('pet1')
!pet1.name := 'Luna'
… 1.000 more pets creation …
!pet1000.name := 'Max'
!insert (p1, pet1) into Ownership
…1.000 more pets associated with p1 …
!insert (p1, pet1000) into Ownership
</object_model>

Output:

**Response**: Unrealistic
**Why**: The object 'p1' of class 'Person' has an age of 250, which exceeds the biologically plausible lifespan of a human. Although it is not plausible that 1 same person owns 1.000 pets.


Example 2:
Input:

<domain_model>
class Car
attributes
    brand: String
end
class Person
attributes
    name: String
end
association Ownership between
    Person [1] role owner
    Car [*] role cars
end
</domain_model>
<object_model>
!new Person('p1')
!p1.age := 19
!new Car('c1')
!c1.brand := 'Toyota'
!insert (p1, c1) into Ownership
</object_model>

Output:

**Response**: Realistic
**Why**: The object 'c1' has a valid, recognized real-world car brand assigned, and its plausible that a teenager has only one car.


Example 3:
Input:

<domain_model>
class Component
attributes
    setting_val: Integer
    config_mode: String
end
</domain_model>
<object_model>
!new Component('c1')
!c1.setting_val := 8080
!c1.config_mode := 'Legacy'
</object_model>

Output:

**Response**: Doubtful
**Why**: The class 'Component' and attribute 'setting_val' are generic and lack specific real-world semantic context. Without knowing what specific physical or software system this represents, it is impossible to determine if '8080' is a realistic value or an outlier.

</examples>

# Conceptual model description:
## Description
The UML model for a Restaurant system is designed to manage various aspects of a restaurant, including reservations, personnel, menu items, and customer preferences. It outlines the core components necessary for managing restaurant operations, customer interactions, and staff assignments.

### Components
1. **DataTypes**
   - `Date`: Encapsulates date information as a string.
   - `Time`: Encapsulates time information as a string.

2. **Enumerations**
   - `SeatingPreference`: Inside, Patio.
   - `SmokingPreference`: Smoking, NonSmoking.
   - `PaymentMethod`: Cash, CreditCard.
   - `ItemType`: Apetizer, Main, Dessert, Beverage.
   - `UnitOfMeasure`: Ounce, Sheet, Pound, Gram, Dozen.
   - `AllergenType`: Lactose, Seafood, Nuts, Gluten.
   - `Diet`: Vegetarian, Vegan, Kosher, Halal.
   - `Language`: English, Spanish, German, Italian.

3. **Classes**
   - `Restaurant`: Represents the restaurant with attributes like name.
   - `Reservation`: Abstract class for handling reservations; includes time, date, and customer details.
     - `Individual`: Inherits from Reservation; adds seating and smoking preferences.
     - `Banquet`: Inherits from Reservation; includes group specifics and payment options.
   - `Table`: Details about tables such as number, description, and capacity.
   - `ItemOrder`: Tracks time of an order.
   - `MenuItem`: Details about menu items, including description, preparation time, and classification.
   - `FoodItem`: Inventory items with attributes such as unit and purchase flag.
   - `Allergen`: Contains allergen type.
   - `Person`: Base class for individuals associated with the restaurant.
     - `Owner`: Inherits from Person; includes percentage shares.
     - `RegularCustomer`: Inherits from Person; includes preferred language.
   - `DietaryRequirement`: Includes dietary information.
   - `ReportedAllergy`: Records allergen type.
   - `Worker`: Abstract class for restaurant employees with common attributes.
     - `HeadWaiter`, `Waiter`, `Manager`, `Cook`, `Chef`, `BusDriver`: Specialized roles with additional attributes (e.g., languages spoken, experience).

## Relationships
- **Restaurant-Owner (RestaurantOwner):** 
  - Multiplicity: Each Restaurant is associated with 1 or more Owners, and each Owner is associated with 1 or more Restaurants.

- **Restaurant-Reservation (RestaurantReservation):** 
  - Multiplicity: Each Restaurant can have 0 or 1 Reservation, and each Reservation can be associated with 0 or more Restaurants.

- **Reservation-RegularCustomer (ReservationCustomer):**
  - Multiplicity: Each Reservation can have 0 or 1 RegularCustomer, and each RegularCustomer can be associated with 0 or more Reservations.

- **Reservation-Waiter (ReservationWaiter):**
  - Multiplicity: Each Reservation is served by 1 or more Waiters, and each Waiter can serve multiple Reservations.

- **Banquet-BusDriver (BanquetBusDriver):**
  - Multiplicity: Each Banquet is associated with exactly 1 BusDriver, but a BusDriver can be associated with 0 or more Banquets.

- **Reservation-Table (ReservationTable):**
  - Multiplicity: Each Reservation is assigned to 1 or more Tables, and each Table can be assigned to multiple Reservations.

- **Reservation-ItemOrder (ReservationItemOrdered):**
  - Multiplicity: Each Reservation can have 0 or more ItemOrders, and each ItemOrder is associated with exactly 1 Reservation.

- **ItemOrder-MenuItem (ItemOrderMenuItem):**
  - Multiplicity: Each ItemOrder is associated with exactly 1 MenuItem, and each MenuItem can be part of multiple ItemOrders.

- **MenuItem-FoodItem (MenuItemFoodItem):**
  - Multiplicity: Each MenuItem utilizes 0 or more FoodItems, and each FoodItem can be utilized by multiple MenuItems.

- **FoodItem-Allergen (FoodItemAllergen):**
  - Multiplicity: Each FoodItem can contain 0 or more Allergens, and each Allergen can apply to multiple FoodItems.

- **MenuItem-Chef (MenuItemChef):**
  - Multiplicity: Each MenuItem is designed by exactly 1 Chef, and each Chef can design multiple MenuItems.

- **Chef-Cook (ChefCook):**
  - Multiplicity: Each Chef supervises 1 or more Cooks, and each Cook is under the supervision of exactly 1 Chef.

- **HeadWaiter-Waiter (HeadWaiterWaiter):**
  - Multiplicity: Each HeadWaiter is responsible for 1 or more Waiters, and each Waiter is accountable to exactly 1 HeadWaiter.

## Invariants
1. **Table Capacity Constraint (PositiveCapacity):** 
   - Every `Table` must have a capacity greater than 0.

2. **Cook Experience Constraint (PositiveExperience):** 
   - A `Cook`'s years of experience must be greater than or equal to 0.

3. **Owner Shares Constraint (TotalOwnerShares):**
   - The sum of percentage shares held by all `Owners` of a `Restaurant` must equal 100.

4. **Reservation Table Capacity Constraint (TablesCapacityGreaterThanPeople):**
   - The total capacity of tables assigned to a `Reservation` must be greater than or equal to the number of people in that reservation.

# Category: Edge Instances
Create an edge case instance. This is an instance that behaves within but at the limit of the expected behavior. This instance must focus on a scenario that is unusual or unlikely in real life but possible according to the syntax and semantics of the model. In terms of semantics, take into account constraints, multiplicities, and uncommon combinations of relationships and attributes.

Continue with the following description, creating the instance according to the syntax example and this specification: 
**Instance: Unlikely Large Banquet with Minimum Staff**

### Description
This scenario imagines a very large banquet event with minimal on-site staff and one absentee owner, but the structure of the event still adheres to all constraints. It ensures that constraints on relationships, capacities, and shares are respected, though it's stretched semantically in an uncommon manner.

---

**Restaurant: Global Feast**  
- Name: Global Feast  
- Owners:
  - **Owner1:** Edward Snow, 49% shares
  - **Owner2:** Olivia Miles, 51% shares
  - Total shares: 100% (constraint met)
  
---

**Reservation: Banquet Event**  
- Type: Banquet
- Date: 2024-02-29 (Leap day, adding rarity)
- Time: 18:00
- Customer: MegaCorp Annual Gala
- Group Size: 300
- Payment Methods: CreditCard
- Regular Customer Associated: None
  
---

**Table Assignments**  
- **Table1:**  
  - Description: "Royal Oak"
  - Capacity: 150
- **Table2:**  
  - Description: "Imperial Silk"
  - Capacity: 150
- Total Capacity: 300 (meets constraint)

---

**Personnel**  
- **BusDriver:** Joshua Kim, associated with Banquet for transport
- **Waiters:**
  - Ahmed Ali (Language: English, Arabic)
  - Carlos Mendes (Language: Spanish, Portuguese)
  - Note: Only two waiters for such a large group makes this unlikely.

- **HeadWaiter:** Annabella Taylor  
  - Manages both waiters, speaks English, and Italian
  
- **Manager:** Yan Zhang
  - Oversees event, speaks English, Chinese

---

**Menu and Kitchen Staff**  
- **MenuItems:**
  - **Appetizer:** Spicy Korean Pancakes  
    - Designed by Chef Hana Park  
  - **Main Dish:** Egyptian Lamb Tagine  
    - Designed by Chef Amir Khalil  
  - **Dessert:** Vegan Chocolate Mousse  
    - Designed by Chef Julia Stein
  
- **Cooks:**
  - Cook under Hana Park: Yuki Tanaka (Japanese)
  - Cook under Amir Khalil: Nadia Aziz (Arabic)
  - Cook under Julia Stein: Pedro Gonzales (French)

- **Chefs Overseeing Items:**
  - **Chef Hana Park**
    - Supervises 1 Cook
    - Languages: Korean, English
  - **Chef Amir Khalil**
    - Supervises 1 Cook
    - Languages: Arabic, English
  - **Chef Julia Stein**
    - Supervises 1 Cook
    - Languages: German, English
  
- **FoodItem Allergens:**
  - **Spicy Korean Pancakes:** Contains Gluten  
  - **Egyptian Lamb Tagine:** Contains Nuts
  - **Vegan Chocolate Mousse:** Contains None

---

### Uncommon Aspects:
- Two owners with perfect complement shares own the restaurant.
- Large reservation of 300 people on a leap day with only one bus driver for transport.
- Limited to only two waiters, which is unusual for such a large banquet, emphasizing this as an edge case.
- Cultural linguistic diversity among staff aligns with the international theme but unlikely for typical operations.

This instance effectively demonstrates the system complying with universally strict structure constraints while pushing semantic edges to create an unlikely, albeit valid, scenario within the restaurant management domain.

The last output is partially incorrect: 
temp.soil> 
temp.soil> !insert (menuitem4, allergen4) into MenuItemFoodItem
<input>:1:0: Participant 2 of association `MenuItemFoodItem' must be of type `FoodItem', but `allergen4' is of type `Allergen'.

temp.soil> 
temp.soil> !insert (menuitem5, allergen5) into MenuItemFoodItem
<input>:1:0: Participant 2 of association `MenuItemFoodItem' must be of type `FoodItem', but `allergen5' is of type `Allergen'.

Please provide the complete output corrected

The last output is partially incorrect: 
checking invariants...
checking invariant (1) `Cook::PositiveExperience': FAILED.
  -> false : Boolean
checking invariant (2) `Reservation::TablesCapacityGreaterThanPeople': OK.
checking invariant (3) `Restaurant::TotalOwnerShares': OK.
checking invariant (4) `Table::PositiveCapacity': OK.
checked 4 invariants in 0.001s, 1 failure.

Invariants
1. **Table Capacity Constraint (PositiveCapacity):** 
   - Every `Table` must have a capacity greater than 0.

2. **Cook Experience Constraint (PositiveExperience):** 
   - A `Cook`'s years of experience must be greater than or equal to 0.

3. **Owner Shares Constraint (TotalOwnerShares):**
   - The sum of percentage shares held by all `Owners` of a `Restaurant` must equal 100.

4. **Reservation Table Capacity Constraint (TablesCapacityGreaterThanPeople):**
   - The total capacity of tables assigned to a `Reservation` must be greater than or equal to the number of people in that reservation.

Please provide the complete output corrected

<domain_model>
model Restaurant

dataType Date
operations
    Date (date : String)
end

dataType Time
operations
   Time (time : String)
end

enum SeatingPreference {
    Inside,
    Patio
}

enum SmokingPreference {
    Smoking,
    NonSmoking
}

enum PaymentMethod {
    Cash,
    CreditCard
}

enum ItemType {
    Apetizer,
    Main,
    Dessert,
    Beverage
}

enum UnitOfMeasure {
    Ounce,
    Sheet,
    Pound,
    Gram,
    Dozen
}

enum AllergenType {
    Lactose,
    Seafood,
    Nuts,
    Gluten
}

enum Diet {
    Vegetarian,
    Vegan,
    Kosher,
    Halal
}

enum Language {
    English,
    Spanish,
    German,
    Italian
}

class Restaurant
attributes
    name : String
end

abstract class Reservation
attributes
    time : Time
    date : Date
    numberPeople : Integer
    name : String
    phoneNumber : String
    number : Integer
end

class Individual < Reservation
attributes
    seating : SeatingPreference
    smoking : SmokingPreference
end

class Banquet < Reservation
attributes
    groupName : String
    paymentMethod : PaymentMethod
    busService : Boolean
end

class Table
attributes
	number : Integer
    description : String
    capacity : Integer
end

class ItemOrder
attributes
    time : Time
end

class MenuItem
attributes
    description : String
    prepTime : Real
    classification : ItemType
end

class FoodItem
attributes
    number : Integer
    description : String
    purchaseFlag : Boolean
    unit : UnitOfMeasure
end

class Allergen
attributes
    type : AllergenType
end

class Person
attributes
	name : String
end

class Owner < Person
attributes
	percentageShares : Integer
end

class RegularCustomer < Person
attributes
	prefferedLanguage : Language
end

class DietaryRequirement
attributes
	diet : Diet
end

class ReportedAllergy
attributes
	allergen : AllergenType
end

abstract class Worker < Person
attributes
	dateOfBirth : Date
    phoneNumber : String
end

class HeadWaiter < Worker
end

class Waiter < Worker
attributes
    spokenLanguage : Language
end

class Manager < Worker
end

class Cook < Worker
attributes
    yearsOfExperience : Integer
end

class Chef < Worker
end

class BusDriver < Worker
attributes
    driverLicenseNr : String
end


association RestaurantOwner between
    Restaurant [1..*]
    Owner [1..*]
end

association RestaurantReservation between
    Restaurant [0..1]
    Reservation [0..*]
end

association ReservationCustomer between
    Reservation [0..*]
    RegularCustomer [0..1]
end

association ReservationWaiter between
    Reservation [*]
    Waiter [1..*] role servedBy
 end

association BanquetBusDriver between
    Banquet [1]
    BusDriver [0..*]
end

association ReservationTable between
    Reservation [1]
    Table [1..*] role assignedTo
end

association ReservationItemOrdered between
    Reservation [1]
    ItemOrder [0..*]
end

association ItemOrderMenuItem between
    ItemOrder [*]
    MenuItem [1] role item
end

association MenuItemFoodItem between
    MenuItem [*] role isUtilized
    FoodItem [*] role utilizes
end

association FoodItemAllergen between
    FoodItem [*]
    Allergen [*] role contains
end

association MenuItemChef between
    MenuItem [*] role designs
    Chef [1] role designedBy
end

association ChefCook between
    Chef [1] role underSupervisionOf
    Cook [1..*] role supervises
end

association HeadWaiterWaiter between
    HeadWaiter [1]
    Waiter [1..*] role responsibleFor
end


constraints
context Table inv PositiveCapacity:
    self.capacity > 0

context Cook inv PositiveExperience:
    self.yearsOfExperience >= 0

context Restaurant inv TotalOwnerShares:
    self.owner -> collect(o | o.percentageShares) -> sum() = 100

context Reservation inv TablesCapacityGreaterThanPeople:
    self.assignedTo -> collect(t | t.capacity) -> sum() >= self.numberPeople
</domain_model>

<object_model>
!new Restaurant('restaurant4')
!restaurant4.name := 'Global Feast'

!new Owner('owner7')
!owner7.name := 'Edward Snow'
!owner7.percentageShares := 49

!new Owner('owner8')
!owner8.name := 'Olivia Miles'
!owner8.percentageShares := 51

!insert (restaurant4, owner7) into RestaurantOwner
!insert (restaurant4, owner8) into RestaurantOwner

!new Banquet('banquet3')
!banquet3.date := Date('2024-02-29')
!banquet3.time := Time('18:00')
!banquet3.groupName := 'MegaCorp Annual Gala'
!banquet3.numberPeople := 300
!banquet3.paymentMethod := #CreditCard

!insert (restaurant4, banquet3) into RestaurantReservation

!new Table('table9')
!table9.number := 1
!table9.description := 'Royal Oak'
!table9.capacity := 150

!new Table('table10')
!table10.number := 2
!table10.description := 'Imperial Silk'
!table10.capacity := 150

!insert (banquet3, table9) into ReservationTable
!insert (banquet3, table10) into ReservationTable

!new BusDriver('busdriver3')
!busdriver3.name := 'Joshua Kim'

!insert (banquet3, busdriver3) into BanquetBusDriver

!new HeadWaiter('headwaiter3')
!headwaiter3.name := 'Annabella Taylor'
!headwaiter3.dateOfBirth := Date('1985-01-01')  -- Arbitrary date of birth
!headwaiter3.phoneNumber := '9090909090'        -- Arbitrary phone number

!new Waiter('waiter5')
!waiter5.name := 'Ahmed Ali'
!waiter5.dateOfBirth := Date('1990-01-01')      -- Arbitrary date of birth
!waiter5.phoneNumber := '1111111111'            -- Arbitrary phone number

!new Waiter('waiter6')
!waiter6.name := 'Carlos Mendes'
!waiter6.dateOfBirth := Date('1992-01-01')      -- Arbitrary date of birth
!waiter6.phoneNumber := '2222222222'            -- Arbitrary phone number

!insert (headwaiter3, waiter5) into HeadWaiterWaiter
!insert (headwaiter3, waiter6) into HeadWaiterWaiter

!insert (banquet3, waiter5) into ReservationWaiter
!insert (banquet3, waiter6) into ReservationWaiter

!new Manager('manager1')
!manager1.name := 'Yan Zhang'
!manager1.dateOfBirth := Date('1978-01-01')     -- Arbitrary date of birth
!manager1.phoneNumber := '3333333333'           -- Arbitrary phone number

!new Chef('chef3')
!chef3.name := 'Hana Park'
!chef3.dateOfBirth := Date('1980-01-01')        -- Arbitrary date of birth
!chef3.phoneNumber := '4444444444'              -- Arbitrary phone number

!new Cook('cook4')
!cook4.name := 'Yuki Tanaka'
!cook4.dateOfBirth := Date('1991-01-01')        -- Arbitrary date of birth
!cook4.phoneNumber := '5555555555'              -- Arbitrary phone number
!cook4.yearsOfExperience := 1                   -- Ensure positive experience

!insert (chef3, cook4) into ChefCook

!new MenuItem('menuitem4')
!menuitem4.description := 'Spicy Korean Pancakes'
!menuitem4.prepTime := 10.0
!menuitem4.classification := #Apetizer

!insert (menuitem4, chef3) into MenuItemChef

!new FoodItem('fooditem8')
!fooditem8.number := 7
!fooditem8.description := 'Ingredient for Spicy Korean Pancakes'
!fooditem8.unit := #Pound

!insert (menuitem4, fooditem8) into MenuItemFoodItem

!new Allergen('allergen4')
!allergen4.type := #Gluten

!insert (fooditem8, allergen4) into FoodItemAllergen

!new Chef('chef4')
!chef4.name := 'Amir Khalil'
!chef4.dateOfBirth := Date('1982-01-01')        -- Arbitrary date of birth
!chef4.phoneNumber := '6666666666'              -- Arbitrary phone number

!new Cook('cook5')
!cook5.name := 'Nadia Aziz'
!cook5.dateOfBirth := Date('1990-01-01')        -- Arbitrary date of birth
!cook5.phoneNumber := '7777777777'              -- Arbitrary phone number
!cook5.yearsOfExperience := 1                   -- Ensure positive experience

!insert (chef4, cook5) into ChefCook

!new MenuItem('menuitem5')
!menuitem5.description := 'Egyptian Lamb Tagine'
!menuitem5.prepTime := 30.0
!menuitem5.classification := #Main

!insert (menuitem5, chef4) into MenuItemChef

!new FoodItem('fooditem9')
!fooditem9.number := 8
!fooditem9.description := 'Ingredient for Egyptian Lamb Tagine'
!fooditem9.unit := #Pound

!insert (menuitem5, fooditem9) into MenuItemFoodItem

!new Allergen('allergen5')
!allergen5.type := #Nuts

!insert (fooditem9, allergen5) into FoodItemAllergen

!new Chef('chef5')
!chef5.name := 'Julia Stein'
!chef5.dateOfBirth := Date('1985-01-01')        -- Arbitrary date of birth
!chef5.phoneNumber := '8888888888'              -- Arbitrary phone number

!new Cook('cook6')
!cook6.name := 'Pedro Gonzales'
!cook6.dateOfBirth := Date('1989-01-01')        -- Arbitrary date of birth
!cook6.phoneNumber := '9999999999'              -- Arbitrary phone number
!cook6.yearsOfExperience := 1                   -- Ensure positive experience

!insert (chef5, cook6) into ChefCook

!new MenuItem('menuitem6')
!menuitem6.description := 'Vegan Chocolate Mousse'
!menuitem6.prepTime := 15.0
!menuitem6.classification := #Dessert

!insert (menuitem6, chef5) into MenuItemChef

!new FoodItem('fooditem10')
!fooditem10.number := 9
!fooditem10.description := 'Ingredient for Vegan Chocolate Mousse'

!insert (menuitem6, fooditem10) into MenuItemFoodItem
</object_model>

Your task is to generate a complete and diverse instance, in plain English, for a given category and based on a provided conceptual model description. The instance must adhere to these requirements: - Be self-contained: Include all required attributes, relationships, and related entities in full detail. - Conform to the model: Fulfill the constraints, multiplicities, relationships, and attributes defined in the class diagram model. - Understand the context: Ensure that its attributes and relationships are relevant. - Avoid duplication of instances: Take into consideration those instances previously built to avoid redundancy. - Semantic diversity: From a semantic point of view, incorporate varied scenarios, including regional, linguistic, or cultural differences. - Structural diversity: Include instances with different numbers of elements, different numbers of relationships and complexity, and create varied examples by changing entity attributes.

You are tasked with creating instances of a conceptual model in the UML-based Specification Environment (USE). You will receive: 1. The UML class diagram that the instance follows. 2. A sample syntax of instances creation. 3. A description of the instance that needs to be created.  Your goal is to generate these instances based on the provided description, adhering strictly to these requirements: - The output must be in plain text, with no additional comments, descriptions, or explanations. - Ensure that the created instance adheres to the provided description. - Follow the syntax sample provided, without deviation. - Take into account previously created instances to avoid using duplicate naming.

<role>
You are an expert software and system modeler. You are able to assess the semantic quality of object models that have been created to conform to a domain model. The models are defined in USE (UML-based Specification Environment) and OCL (Object Constraint Language).

Your primary capability is "Semantic Reality Checking". You do not just check for syntactic correctness; you check for real-world plausibility and logical consistency within a given domain.
</role>

<context>
The user will provide two types of content:
1. **Domain Model (.use)**: A class diagram definition including classes, attributes, enums, relationships, multiplicities and roles.
2. **Object Model (.soil)**: An object model. This object model can be seen as a script composed of instructions for the creation of objects, relationships and setting attribute values (snapshot).

Your goal is to act as a judge to determine if the object model represents a **REALISTIC** scenario based on the domain model and common sense real-world logic.
</context>

<definitions>
- **Realistic**: The object model is syntactically correct AND semantically plausible (e.g., A 'Person' has an age between 0 and 120; a 'Car' has a positive price).
- **Unrealistic**: The object model contains contradictions, impossible physical values, or nonsensical relationships (e.g., A 'Person' is their own father; a 'Product' has a negative weight).
- **Doubtful**: You cannot determine whether the object model is realistic or not.
</definitions>

<instructions>
Follow this thinking process strictly before generating the final output:

1. **Analyze the Domain (.use)**: Understand the classes and what they represent in the real world.
2. **Analyze the Instances (.soil)**: Map the created objects to their classes. Look at the specific values assigned to attributes and the relationships created between objects.
3. **Evaluate Semantics**:
    - Apply "Common Sense Knowledge" to the attribute values.
    - Check cardinality and relationship logic beyond simple OCL constraints.
    - Identify any outliers or logical fallacies.
4. **Determine Verdict**: Select one of the defined labels (Realistic/Unrealistic/Doubtful).
</instructions>

<constraints>
- **Tone**: Objective, Analytical, Technical.
- **Verbosity**: Low. Be direct.
- **Reasoning**: The "Why" section must be concise and specific, citing variable names, objects, or relationships when possible.
- Do not output the internal thinking process. Only output the final formatted result.
</constraints>

<output_format>
Structure your response exactly as follows:

**Response**: [Realistic | Unrealistic | Doubtful]
**Why**: [Concise explanation of your reasoning. If Unrealistic, specify the exact objects, values or relationships that break realism.]
</output_format>

<examples>
Example 1:
Input:

<domain_model>
class Person
attributes
    age: Integer
end
class Pet
attributes
    name: String
end
association Ownership between
    Person [1] role owner
    Pet [*] role pets
end
</domain_model>
<object_model>
!new Person('p1')
!p1.age := 250
!new Pet('pet1')
!pet1.name := 'Luna'
… 1.000 more pets creation …
!pet1000.name := 'Max'
!insert (p1, pet1) into Ownership
…1.000 more pets associated with p1 …
!insert (p1, pet1000) into Ownership
</object_model>

Output:

**Response**: Unrealistic
**Why**: The object 'p1' of class 'Person' has an age of 250, which exceeds the biologically plausible lifespan of a human. Although it is not plausible that 1 same person owns 1.000 pets.


Example 2:
Input:

<domain_model>
class Car
attributes
    brand: String
end
class Person
attributes
    name: String
end
association Ownership between
    Person [1] role owner
    Car [*] role cars
end
</domain_model>
<object_model>
!new Person('p1')
!p1.age := 19
!new Car('c1')
!c1.brand := 'Toyota'
!insert (p1, c1) into Ownership
</object_model>

Output:

**Response**: Realistic
**Why**: The object 'c1' has a valid, recognized real-world car brand assigned, and its plausible that a teenager has only one car.


Example 3:
Input:

<domain_model>
class Component
attributes
    setting_val: Integer
    config_mode: String
end
</domain_model>
<object_model>
!new Component('c1')
!c1.setting_val := 8080
!c1.config_mode := 'Legacy'
</object_model>

Output:

**Response**: Doubtful
**Why**: The class 'Component' and attribute 'setting_val' are generic and lack specific real-world semantic context. Without knowing what specific physical or software system this represents, it is impossible to determine if '8080' is a realistic value or an outlier.

</examples>

# Conceptual model description:
## Description
The UML model for a Restaurant system is designed to manage various aspects of a restaurant, including reservations, personnel, menu items, and customer preferences. It outlines the core components necessary for managing restaurant operations, customer interactions, and staff assignments.

### Components
1. **DataTypes**
   - `Date`: Encapsulates date information as a string.
   - `Time`: Encapsulates time information as a string.

2. **Enumerations**
   - `SeatingPreference`: Inside, Patio.
   - `SmokingPreference`: Smoking, NonSmoking.
   - `PaymentMethod`: Cash, CreditCard.
   - `ItemType`: Apetizer, Main, Dessert, Beverage.
   - `UnitOfMeasure`: Ounce, Sheet, Pound, Gram, Dozen.
   - `AllergenType`: Lactose, Seafood, Nuts, Gluten.
   - `Diet`: Vegetarian, Vegan, Kosher, Halal.
   - `Language`: English, Spanish, German, Italian.

3. **Classes**
   - `Restaurant`: Represents the restaurant with attributes like name.
   - `Reservation`: Abstract class for handling reservations; includes time, date, and customer details.
     - `Individual`: Inherits from Reservation; adds seating and smoking preferences.
     - `Banquet`: Inherits from Reservation; includes group specifics and payment options.
   - `Table`: Details about tables such as number, description, and capacity.
   - `ItemOrder`: Tracks time of an order.
   - `MenuItem`: Details about menu items, including description, preparation time, and classification.
   - `FoodItem`: Inventory items with attributes such as unit and purchase flag.
   - `Allergen`: Contains allergen type.
   - `Person`: Base class for individuals associated with the restaurant.
     - `Owner`: Inherits from Person; includes percentage shares.
     - `RegularCustomer`: Inherits from Person; includes preferred language.
   - `DietaryRequirement`: Includes dietary information.
   - `ReportedAllergy`: Records allergen type.
   - `Worker`: Abstract class for restaurant employees with common attributes.
     - `HeadWaiter`, `Waiter`, `Manager`, `Cook`, `Chef`, `BusDriver`: Specialized roles with additional attributes (e.g., languages spoken, experience).

## Relationships
- **Restaurant-Owner (RestaurantOwner):** 
  - Multiplicity: Each Restaurant is associated with 1 or more Owners, and each Owner is associated with 1 or more Restaurants.

- **Restaurant-Reservation (RestaurantReservation):** 
  - Multiplicity: Each Restaurant can have 0 or 1 Reservation, and each Reservation can be associated with 0 or more Restaurants.

- **Reservation-RegularCustomer (ReservationCustomer):**
  - Multiplicity: Each Reservation can have 0 or 1 RegularCustomer, and each RegularCustomer can be associated with 0 or more Reservations.

- **Reservation-Waiter (ReservationWaiter):**
  - Multiplicity: Each Reservation is served by 1 or more Waiters, and each Waiter can serve multiple Reservations.

- **Banquet-BusDriver (BanquetBusDriver):**
  - Multiplicity: Each Banquet is associated with exactly 1 BusDriver, but a BusDriver can be associated with 0 or more Banquets.

- **Reservation-Table (ReservationTable):**
  - Multiplicity: Each Reservation is assigned to 1 or more Tables, and each Table can be assigned to multiple Reservations.

- **Reservation-ItemOrder (ReservationItemOrdered):**
  - Multiplicity: Each Reservation can have 0 or more ItemOrders, and each ItemOrder is associated with exactly 1 Reservation.

- **ItemOrder-MenuItem (ItemOrderMenuItem):**
  - Multiplicity: Each ItemOrder is associated with exactly 1 MenuItem, and each MenuItem can be part of multiple ItemOrders.

- **MenuItem-FoodItem (MenuItemFoodItem):**
  - Multiplicity: Each MenuItem utilizes 0 or more FoodItems, and each FoodItem can be utilized by multiple MenuItems.

- **FoodItem-Allergen (FoodItemAllergen):**
  - Multiplicity: Each FoodItem can contain 0 or more Allergens, and each Allergen can apply to multiple FoodItems.

- **MenuItem-Chef (MenuItemChef):**
  - Multiplicity: Each MenuItem is designed by exactly 1 Chef, and each Chef can design multiple MenuItems.

- **Chef-Cook (ChefCook):**
  - Multiplicity: Each Chef supervises 1 or more Cooks, and each Cook is under the supervision of exactly 1 Chef.

- **HeadWaiter-Waiter (HeadWaiterWaiter):**
  - Multiplicity: Each HeadWaiter is responsible for 1 or more Waiters, and each Waiter is accountable to exactly 1 HeadWaiter.

## Invariants
1. **Table Capacity Constraint (PositiveCapacity):** 
   - Every `Table` must have a capacity greater than 0.

2. **Cook Experience Constraint (PositiveExperience):** 
   - A `Cook`'s years of experience must be greater than or equal to 0.

3. **Owner Shares Constraint (TotalOwnerShares):**
   - The sum of percentage shares held by all `Owners` of a `Restaurant` must equal 100.

4. **Reservation Table Capacity Constraint (TablesCapacityGreaterThanPeople):**
   - The total capacity of tables assigned to a `Reservation` must be greater than or equal to the number of people in that reservation.

# Category: Overconstraint Detection
Create an instance that represents a real-life scenario that is logically valid but violates the model's multiplicities or constraints, exposing overly restrictive or unrealistic restrictions.

# UML class diagram:
model Restaurant

dataType Date
operations
    Date (date : String)
end

dataType Time
operations
   Time (time : String)
end

enum SeatingPreference {
    Inside,
    Patio
}

enum SmokingPreference {
    Smoking,
    NonSmoking
}

enum PaymentMethod {
    Cash,
    CreditCard
}

enum ItemType {
    Apetizer,
    Main,
    Dessert,
    Beverage
}

enum UnitOfMeasure {
    Ounce,
    Sheet,
    Pound,
    Gram,
    Dozen
}

enum AllergenType {
    Lactose,
    Seafood,
    Nuts,
    Gluten
}

enum Diet {
    Vegetarian,
    Vegan,
    Kosher,
    Halal
}

enum Language {
    English,
    Spanish,
    German,
    Italian
}

class Restaurant
attributes
    name : String
end

abstract class Reservation
attributes
    time : Time
    date : Date
    numberPeople : Integer
    name : String
    phoneNumber : String
    number : Integer
end

class Individual < Reservation
attributes
    seating : SeatingPreference
    smoking : SmokingPreference
end

class Banquet < Reservation
attributes
    groupName : String
    paymentMethod : PaymentMethod
    busService : Boolean
end

class Table
attributes
	number : Integer
    description : String
    capacity : Integer
end

class ItemOrder
attributes
    time : Time
end

class MenuItem
attributes
    description : String
    prepTime : Real
    classification : ItemType
end

class FoodItem
attributes
    number : Integer
    description : String
    purchaseFlag : Boolean
    unit : UnitOfMeasure
end

class Allergen
attributes
    type : AllergenType
end

class Person
attributes
	name : String
end

class Owner < Person
attributes
	percentageShares : Integer
end

class RegularCustomer < Person
attributes
	prefferedLanguage : Language
end

class DietaryRequirement
attributes
	diet : Diet
end

class ReportedAllergy
attributes
	allergen : AllergenType
end

abstract class Worker < Person
attributes
	dateOfBirth : Date
    phoneNumber : String
end

class HeadWaiter < Worker
end

class Waiter < Worker
attributes
    spokenLanguage : Language
end

class Manager < Worker
end

class Cook < Worker
attributes
    yearsOfExperience : Integer
end

class Chef < Worker
end

class BusDriver < Worker
attributes
    driverLicenseNr : String
end


association RestaurantOwner between
    Restaurant [1..*]
    Owner [1..*]
end

association RestaurantReservation between
    Restaurant [0..1]
    Reservation [0..*]
end

association ReservationCustomer between
    Reservation [0..*]
    RegularCustomer [0..1]
end

association ReservationWaiter between
    Reservation [*]
    Waiter [1..*] role servedBy
 end

association BanquetBusDriver between
    Banquet [1]
    BusDriver [0..*]
end

association ReservationTable between
    Reservation [1]
    Table [1..*] role assignedTo
end

association ReservationItemOrdered between
    Reservation [1]
    ItemOrder [0..*]
end

association ItemOrderMenuItem between
    ItemOrder [*]
    MenuItem [1] role item
end

association MenuItemFoodItem between
    MenuItem [*] role isUtilized
    FoodItem [*] role utilizes
end

association FoodItemAllergen between
    FoodItem [*]
    Allergen [*] role contains
end

association MenuItemChef between
    MenuItem [*] role designs
    Chef [1] role designedBy
end

association ChefCook between
    Chef [1] role underSupervisionOf
    Cook [1..*] role supervises
end

association HeadWaiterWaiter between
    HeadWaiter [1]
    Waiter [1..*] role responsibleFor
end


constraints
context Table inv PositiveCapacity:
    self.capacity > 0

context Cook inv PositiveExperience:
    self.yearsOfExperience >= 0

context Restaurant inv TotalOwnerShares:
    self.owner -> collect(o | o.percentageShares) -> sum() = 100

context Reservation inv TablesCapacityGreaterThanPeople:
    self.assignedTo -> collect(t | t.capacity) -> sum() >= self.numberPeople

# Syntax example of instances creation:
-- This is a comment example

-- Primitive data types:
    -- Integer i.e. 1, 2, 3, etc.
    -- Real i.e. 1.0, 21.89, 322.05556, etc.
    -- Boolean i.e. true or false
    -- String i.e. 'Hello World'

-- You can create instances with the following syntax:
!new <instance type>('<instance name>')
-- Example:
!new Client('client1')
!new Store('store4')

-- You can assign values to attributes for a created instance with the following syntax:
!<instance name>.<attribute name> := <value>
-- Example for different data types:
!client1.clientId := 1 -- For Integer
!client1.balance := 1123.45 -- For Real
!client1.name := 'John' -- For Strings
!store4.available := true -- For Boolean

-- You can create associations between instances with the following syntax:
!insert (<instance name1>, <instance name2>) into <association name>
-- Example:
!insert (client1, store4) into ClientStore

-- Custom data types usage:
    -- dataType Location
    -- operations
    --   Location(x : Real, y : Real)
    --   some other operations
    -- end
-- You can create custom data types by calling the constructor directly; in this case, the constructor of Location requires two arguments: x and y of type Real. So it can be used as follows:
!store4.location := Location(14.0, 289.0)

-- Enums usage:
    -- enum Type { Clothes, Shoes }
-- Can be used as follows:
!store4.type := #Clothes

# Instance description:
Please create the instance according to this specification:
## Instance: Celebration Banquet at "The Global Table"

### Entities:

1. **Restaurant:**
   - Name: The Global Table

2. **Owner:**
   - Name: Maria Gonzales
   - Percentage Shares: 60%

3. **Owner:**
   - Name: John Smith
   - Percentage Shares: 40%

4. **Banquet (Reservation):**
   - Date: "2023-12-15"
   - Time: "18:00"
   - Group Name: International Business Forum
   - Number of People: 120
   - Payment Method: CreditCard

5. **Table (Assigned to Banquet):**
   - Number: T1
   - Description: Large rectangle table
   - Capacity: 12

6. **Table (Assigned to Banquet):**
   - Number: T2
   - Description: Standard round table
   - Capacity: 8

7. **Table (Assigned to Banquet):**
   - Number: T3
   - Description: Square table
   - Capacity: 4

8. **Table (Assigned to Banquet):**
   - Number: T4
   - Description: Oval table
   - Capacity: 10

9. **BusDriver:**
   - Name: Alexei Petrov
   - Language: Russian, English

### Relationships:

1. **Restaurant-Owner (RestaurantOwner):**
   - The Global Table - Maria Gonzales
   - The Global Table - John Smith

2. **Restaurant-Reservation (RestaurantReservation):**
   - The Global Table - International Business Forum Banquet

3. **Banquet-BusDriver (BanquetBusDriver):**
   - International Business Forum Banquet - Alexei Petrov

4. **Reservation-Table (ReservationTable - Violates Constraint):**
   - International Business Forum Banquet is assigned with T1, T2, T3, T4
   
### Explanation of Overconstraint Detection:

In this instance, the Banquet reservation for the International Business Forum is for 120 people. The tables assigned to the banquet (T1, T2, T3, T4) total to a capacity of only 34, violating the 'TablesCapacityGreaterThanPeople' invariant, which requires the table capacity to match or exceed the number of people in the reservation. This scenario exposes a flaw that might occur in real-world settings where table capacities or reservation plans are miscommunicated or miscalculated. It demonstrates how enforcing such constraints without flexibility could lead to errors or logistical issues, especially in large or complex events.

The last output is partially incorrect: 
temp.soil> !new Banquet('banquet1')
temp.soil> !banquet1.date := Date("2023-12-15")
<input>:line 1:8 mismatched input '.' expecting :=

temp.soil> !banquet1.time := Time("18:00")
<input>:line 1:8 mismatched input '.' expecting :=

Please provide the complete output corrected

<domain_model>
model Restaurant

dataType Date
operations
    Date (date : String)
end

dataType Time
operations
   Time (time : String)
end

enum SeatingPreference {
    Inside,
    Patio
}

enum SmokingPreference {
    Smoking,
    NonSmoking
}

enum PaymentMethod {
    Cash,
    CreditCard
}

enum ItemType {
    Apetizer,
    Main,
    Dessert,
    Beverage
}

enum UnitOfMeasure {
    Ounce,
    Sheet,
    Pound,
    Gram,
    Dozen
}

enum AllergenType {
    Lactose,
    Seafood,
    Nuts,
    Gluten
}

enum Diet {
    Vegetarian,
    Vegan,
    Kosher,
    Halal
}

enum Language {
    English,
    Spanish,
    German,
    Italian
}

class Restaurant
attributes
    name : String
end

abstract class Reservation
attributes
    time : Time
    date : Date
    numberPeople : Integer
    name : String
    phoneNumber : String
    number : Integer
end

class Individual < Reservation
attributes
    seating : SeatingPreference
    smoking : SmokingPreference
end

class Banquet < Reservation
attributes
    groupName : String
    paymentMethod : PaymentMethod
    busService : Boolean
end

class Table
attributes
	number : Integer
    description : String
    capacity : Integer
end

class ItemOrder
attributes
    time : Time
end

class MenuItem
attributes
    description : String
    prepTime : Real
    classification : ItemType
end

class FoodItem
attributes
    number : Integer
    description : String
    purchaseFlag : Boolean
    unit : UnitOfMeasure
end

class Allergen
attributes
    type : AllergenType
end

class Person
attributes
	name : String
end

class Owner < Person
attributes
	percentageShares : Integer
end

class RegularCustomer < Person
attributes
	prefferedLanguage : Language
end

class DietaryRequirement
attributes
	diet : Diet
end

class ReportedAllergy
attributes
	allergen : AllergenType
end

abstract class Worker < Person
attributes
	dateOfBirth : Date
    phoneNumber : String
end

class HeadWaiter < Worker
end

class Waiter < Worker
attributes
    spokenLanguage : Language
end

class Manager < Worker
end

class Cook < Worker
attributes
    yearsOfExperience : Integer
end

class Chef < Worker
end

class BusDriver < Worker
attributes
    driverLicenseNr : String
end


association RestaurantOwner between
    Restaurant [1..*]
    Owner [1..*]
end

association RestaurantReservation between
    Restaurant [0..1]
    Reservation [0..*]
end

association ReservationCustomer between
    Reservation [0..*]
    RegularCustomer [0..1]
end

association ReservationWaiter between
    Reservation [*]
    Waiter [1..*] role servedBy
 end

association BanquetBusDriver between
    Banquet [1]
    BusDriver [0..*]
end

association ReservationTable between
    Reservation [1]
    Table [1..*] role assignedTo
end

association ReservationItemOrdered between
    Reservation [1]
    ItemOrder [0..*]
end

association ItemOrderMenuItem between
    ItemOrder [*]
    MenuItem [1] role item
end

association MenuItemFoodItem between
    MenuItem [*] role isUtilized
    FoodItem [*] role utilizes
end

association FoodItemAllergen between
    FoodItem [*]
    Allergen [*] role contains
end

association MenuItemChef between
    MenuItem [*] role designs
    Chef [1] role designedBy
end

association ChefCook between
    Chef [1] role underSupervisionOf
    Cook [1..*] role supervises
end

association HeadWaiterWaiter between
    HeadWaiter [1]
    Waiter [1..*] role responsibleFor
end


constraints
context Table inv PositiveCapacity:
    self.capacity > 0

context Cook inv PositiveExperience:
    self.yearsOfExperience >= 0

context Restaurant inv TotalOwnerShares:
    self.owner -> collect(o | o.percentageShares) -> sum() = 100

context Reservation inv TablesCapacityGreaterThanPeople:
    self.assignedTo -> collect(t | t.capacity) -> sum() >= self.numberPeople
</domain_model>

<object_model>
!new Restaurant('restaurant1')
!restaurant1.name := 'The Global Table'

!new Owner('owner1')
!owner1.name := 'Maria Gonzales'
!owner1.percentageShares := 60

!new Owner('owner2')
!owner2.name := 'John Smith'
!owner2.percentageShares := 40

!insert (restaurant1, owner1) into RestaurantOwner
!insert (restaurant1, owner2) into RestaurantOwner

!new Banquet('banquet1')
!banquet1.date := Date('2023-12-15')
!banquet1.time := Time('18:00')
!banquet1.groupName := 'International Business Forum'
!banquet1.numberPeople := 120
!banquet1.paymentMethod := #CreditCard

!insert (restaurant1, banquet1) into RestaurantReservation

!new Table('table1')
!table1.number := 1
!table1.description := 'Large rectangle table'
!table1.capacity := 12

!new Table('table2')
!table2.number := 2
!table2.description := 'Standard round table'
!table2.capacity := 8

!new Table('table3')
!table3.number := 3
!table3.description := 'Square table'
!table3.capacity := 4

!new Table('table4')
!table4.number := 4
!table4.description := 'Oval table'
!table4.capacity := 10

!insert (banquet1, table1) into ReservationTable
!insert (banquet1, table2) into ReservationTable
!insert (banquet1, table3) into ReservationTable
!insert (banquet1, table4) into ReservationTable

!new BusDriver('busdriver1')
!busdriver1.name := 'Alexei Petrov'

!insert (banquet1, busdriver1) into BanquetBusDriver
</object_model>