AddressBook / gen6

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>

For the same category and model description, generate another instance that is structurally and semantically different from the previous ones

Continue with the following description, creating the instance according to the syntax example and this specification: 
## Instance: Transcontinental Business Network

### Address Book
- **Name**: Transcontinental Business Network

### Contacts

#### 1. Person Contact
- **Name**: Ana Silva
- **Phone**: +55-21-98765-4321
- **Website**: www.anasilva.br
- **Email**: ana.silva@southamericatraders.br
- **Title**: International Trade Manager

##### Notes for Ana Silva
1. **Note**
   - **Author**: Ana Silva
   - **Time**: "2023-01-18"
   - **Type**: CALL
   - **Comment**: Confirm shipment details with European partners post-Brexit.

##### Address for Ana Silva
- **City**: Rio de Janeiro
- **House Number**: 50
- **Street**: Avenida Atlântica

##### Relationships for Ana Silva
1. **Relationship**
   - **Type**: BOSS
   - **Target**: Miguel Santana

2. **Relationship**
   - **Type**: COWORKER
   - **Target**: Emma Li

#### 2. Company Contact
- **Name**: Panther Logistics
- **Phone**: +49-30-555-6666
- **Website**: www.pantherlogistics.de
- **Email**: contact@pantherlogistics.de
- **Industry**: Logistics and Supply Chain

##### Notes for Panther Logistics
- **Note**
  - **Author**: Manfred Bauer
  - **Time**: "2023-03-01"
  - **Type**: MEETING
  - **Comment**: Discuss logistics optimization for the new cargo routes.

##### Address for Panther Logistics
1. **Address**
   - **City**: Berlin
   - **House Number**: 18
   - **Street**: Potsdamer Straße

#### 3. Person Contact
- **Name**: Miguel Santana
- **Phone**: +34-622-555-9933
- **Website**: www.miguelsantana.es
- **Email**: miguel.santana@esolutions.es
- **Title**: Procurement Specialist

##### Notes for Miguel Santana
- **Note**
  - **Author**: Miguel Santana
  - **Time**: "2023-05-30"
  - **Type**: EMAIL
  - **Comment**: Recommendations for sourcing sustainable materials from Asia.

##### Address for Miguel Santana
- **City**: Madrid
- **House Number**: 10
- **Street**: Gran Vía

##### Relationships for Miguel Santana
- **Relationship**
  - **Type**: EMPLOYEE
  - **Target**: Ana Silva

#### 4. Person Contact
- **Name**: Emma Li
- **Phone**: +86-10-6655-2233
- **Website**: www.emmali.cn
- **Email**: emma.li@chinabusiness.cn
- **Title**: Regional Sales Director

##### Notes for Emma Li
- **Note**
  - **Author**: Emma Li
  - **Time**: "2023-06-15"
  - **Type**: EMAIL
  - **Comment**: Quarterly sales performance review with stakeholders.

##### Address for Emma Li
- **City**: Beijing
- **House Number**: 47
- **Street**: Dongcheng Street

##### Relationships for Emma Li
1. **Relationship**
   - **Type**: SUBDIVISION
   - **Target**: Panther Logistics

2. **Relationship**
   - **Type**: COWORKER
   - **Target**: Ana Silva

### Relationships

- **Ana Silva** is the **BOSS** of **Miguel Santana**.
- **Miguel Santana** is an **EMPLOYEE** under **Ana Silva**.
- **Ana Silva** and **Emma Li** collaborate as **COWORKERS**.
- **Emma Li** manages some **SUBDIVISION** aspects in collaboration with **Panther Logistics**.

This instance captures the vibrant international connections centered around trade, logistics, and supply chain management across various continents. It introduces the complexity of trade agreements post-Brexit and their effects on business practices, indicating nuanced intercorporate and interpersonal relationships in a rapidly evolving global market.

<domain_model>
model AddressBook

enum NoteType {
    MEETING,
    CALL,
    EMAIL
}

enum RelationshipType {
    BOSS,
    EMPLOYEE,
    SUBDIVISION,
    COWORKER
}

dataType Date
operations
    Date(date : String)
end

class AddressBook
end

abstract class Contact
attributes
    name : String
    phone : String
    website : String
    email : String
end

class Note
attributes
    author : String
    time : Date
    type : NoteType
    comment : String
end

class Company < Contact
attributes
    industry : String
end

class Person < Contact
attributes
    title : String
end

class Address
attributes
    city : String
    houseNr : String
    street : String
end

class Relationship
attributes
    type : RelationshipType
end

composition AddressBookMadeOfContact between
    AddressBook[1]
    Contact[*]
end

composition ContactContainsNote between
    Contact[1]
    Note[*]
end

association RelationshipToContact between
    Relationship[*] role isRelated
    Contact[1] role target
end

composition ContactToRelationship between
    Contact[1]
    Relationship[*] role relates
end

composition ContactContainsAddress between
    Contact[1] role source
    Address[*] role address
end


constraints
context Contact inv DifferentSourceTarget:
    self.relates->forAll(r | r.target<>self)
</domain_model>

<object_model>
!new AddressBook('TranscontinentalBusinessNetwork')

!new Person('AnaSilva')
!AnaSilva.name := 'Ana Silva'
!AnaSilva.phone := '+55-21-98765-4321'
!AnaSilva.website := 'www.anasilva.br'
!AnaSilva.email := 'ana.silva@southamericatraders.br'
!AnaSilva.title := 'International Trade Manager'

!new Address('AnaSilvaAddress')
!AnaSilvaAddress.city := 'Rio de Janeiro'
!AnaSilvaAddress.houseNr := '50'
!AnaSilvaAddress.street := 'Avenida Atlântica'
!insert (AnaSilva, AnaSilvaAddress) into ContactContainsAddress

!new Note('AnaSilvaNote')
!AnaSilvaNote.author := 'Ana Silva'
!AnaSilvaNote.time := Date('2023-01-18')
!AnaSilvaNote.type := #CALL
!AnaSilvaNote.comment := 'Confirm shipment details with European partners post-Brexit.'
!insert (AnaSilva, AnaSilvaNote) into ContactContainsNote

!new Company('PantherLogistics')
!PantherLogistics.name := 'Panther Logistics'
!PantherLogistics.phone := '+49-30-555-6666'
!PantherLogistics.website := 'www.pantherlogistics.de'
!PantherLogistics.email := 'contact@pantherlogistics.de'
!PantherLogistics.industry := 'Logistics and Supply Chain'

!new Address('PantherLogisticsAddress')
!PantherLogisticsAddress.city := 'Berlin'
!PantherLogisticsAddress.houseNr := '18'
!PantherLogisticsAddress.street := 'Potsdamer Straße'
!insert (PantherLogistics, PantherLogisticsAddress) into ContactContainsAddress

!new Note('PantherLogisticsNote')
!PantherLogisticsNote.author := 'Manfred Bauer'
!PantherLogisticsNote.time := Date('2023-03-01')
!PantherLogisticsNote.type := #MEETING
!PantherLogisticsNote.comment := 'Discuss logistics optimization for the new cargo routes.'
!insert (PantherLogistics, PantherLogisticsNote) into ContactContainsNote

!new Person('MiguelSantana')
!MiguelSantana.name := 'Miguel Santana'
!MiguelSantana.phone := '+34-622-555-9933'
!MiguelSantana.website := 'www.miguelsantana.es'
!MiguelSantana.email := 'miguel.santana@esolutions.es'
!MiguelSantana.title := 'Procurement Specialist'

!new Address('MiguelSantanaAddress')
!MiguelSantanaAddress.city := 'Madrid'
!MiguelSantanaAddress.houseNr := '10'
!MiguelSantanaAddress.street := 'Gran Vía'
!insert (MiguelSantana, MiguelSantanaAddress) into ContactContainsAddress

!new Note('MiguelSantanaNote')
!MiguelSantanaNote.author := 'Miguel Santana'
!MiguelSantanaNote.time := Date('2023-05-30')
!MiguelSantanaNote.type := #EMAIL
!MiguelSantanaNote.comment := 'Recommendations for sourcing sustainable materials from Asia.'
!insert (MiguelSantana, MiguelSantanaNote) into ContactContainsNote

!new Person('EmmaLi')
!EmmaLi.name := 'Emma Li'
!EmmaLi.phone := '+86-10-6655-2233'
!EmmaLi.website := 'www.emmali.cn'
!EmmaLi.email := 'emma.li@chinabusiness.cn'
!EmmaLi.title := 'Regional Sales Director'

!new Address('EmmaLiAddress')
!EmmaLiAddress.city := 'Beijing'
!EmmaLiAddress.houseNr := '47'
!EmmaLiAddress.street := 'Dongcheng Street'
!insert (EmmaLi, EmmaLiAddress) into ContactContainsAddress

!new Note('EmmaLiNote')
!EmmaLiNote.author := 'Emma Li'
!EmmaLiNote.time := Date('2023-06-15')
!EmmaLiNote.type := #EMAIL
!EmmaLiNote.comment := 'Quarterly sales performance review with stakeholders.'
!insert (EmmaLi, EmmaLiNote) into ContactContainsNote

!new Relationship('AnaToMiguelBoss')
!AnaToMiguelBoss.type := #BOSS
!insert (AnaToMiguelBoss, MiguelSantana) into RelationshipToContact
!insert (AnaSilva, AnaToMiguelBoss) into ContactToRelationship

!new Relationship('MiguelToAnaEmployee')
!MiguelToAnaEmployee.type := #EMPLOYEE
!insert (MiguelToAnaEmployee, AnaSilva) into RelationshipToContact
!insert (MiguelSantana, MiguelToAnaEmployee) into ContactToRelationship

!new Relationship('AnaToEmmaCoworker')
!AnaToEmmaCoworker.type := #COWORKER
!insert (AnaToEmmaCoworker, EmmaLi) into RelationshipToContact
!insert (AnaSilva, AnaToEmmaCoworker) into ContactToRelationship

!new Relationship('EmmaToPantherSubdivision')
!EmmaToPantherSubdivision.type := #SUBDIVISION
!insert (EmmaToPantherSubdivision, PantherLogistics) into RelationshipToContact
!insert (EmmaLi, EmmaToPantherSubdivision) into ContactToRelationship

!insert (TranscontinentalBusinessNetwork, AnaSilva) into AddressBookMadeOfContact
!insert (TranscontinentalBusinessNetwork, PantherLogistics) into AddressBookMadeOfContact
!insert (TranscontinentalBusinessNetwork, MiguelSantana) into AddressBookMadeOfContact
!insert (TranscontinentalBusinessNetwork, EmmaLi) into AddressBookMadeOfContact
</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>

For the same category and model description, generate another instance that is structurally and semantically different from the previous ones

Continue with the following description, creating the instance according to the syntax example and this specification: 
Instance: "World Culinary Network Address Book"

### Address Book
- **AddressBook**: "World Culinary Network Address Book"
  - This address book is tailored for chefs, culinary schools, and restaurant groups focusing on international culinary arts and connections.

### Contacts
- **Contact 1**: "Gourmet Group Inc."
  - **Type**: Company
  - **Attributes**:
    - Name: Gourmet Group Inc.
    - Phone: +1-212-555-1020
    - Website: www.gourmetgroup.com
    - Email: inquiries@gourmetgroup.com
    - Industry: Hospitality & Food
  - **Addresses**:
    - Address 1:
      - City: New York
      - HouseNr: 750
      - Street: Culinary Plaza

- **Contact 2**: "Chef Pierre Dubois"
  - **Type**: Person
  - **Attributes**:
    - Name: Chef Pierre Dubois
    - Phone: +33-1-555-0654
    - Website: 
    - Email: pierre.dubois@frenchflavor.fr
    - Title: Executive Chef
  - **Addresses**:
    - Address 1:
      - City: Paris
      - HouseNr: 66
      - Street: Rue de la Cuisine
  - **Notes**:
    - Note 1:
      - Author: Gourmet Group Inc.
      - Time: "2023-10-07"
      - Type: EMAIL
      - Comment: Sent invitation to Global Culinary Summit.

- **Contact 3**: "Asian Culinary Academy"
  - **Type**: Company
  - **Attributes**:
    - Name: Asian Culinary Academy
    - Phone: +81-3-5550-2208
    - Website: www.asianculinary.ac.jp
    - Email: info@asianculinary.ac.jp
    - Industry: Education
  - **Addresses**:
    - (Boundary case with no addresses)

- **Contact 4**: "Chef Maria Lopez"
  - **Type**: Person
  - **Attributes**:
    - Name: Chef Maria Lopez
    - Phone: +34-91-555-0423
    - Website: www.chefmaria.es
    - Email: maria.lopez@innovocuisine.es
    - Title: Pastry Chef
  - **Addresses**:
    - Address 1:
      - City: Madrid
      - HouseNr: 99
      - Street: Dulce Street
    - Address 2:
      - City: Barcelona
      - HouseNr: 88
      - Street: Pastelería Avenue

### Relationships
- **Relationship 1**: Between "Gourmet Group Inc." and "Chef Pierre Dubois"
  - **Type**: BOSS
  - Target: Chef Pierre Dubois

- **Relationship 2**: Between "Chef Maria Lopez" and "Asian Culinary Academy"
  - **Type**: EMPLOYEE
  - Target: Asian Culinary Academy

- **Relationship 3**: Between "Chef Pierre Dubois" and "Chef Maria Lopez"
  - **Type**: COWORKER
  - Target: Chef Maria Lopez

### Boundary Considerations
- "Asian Culinary Academy" is structured without an address, focusing on the virtual or non-fixed location for culinary education.
- A mix of chefs with different specialties and locations, including Parisian and Spanish pastry experts, illustrates an eclectic culinary network.
- Multiple addresses for Chef Maria Lopez reflect a direct engagement in various culinary activities across Spain.

<domain_model>
model AddressBook

enum NoteType {
    MEETING,
    CALL,
    EMAIL
}

enum RelationshipType {
    BOSS,
    EMPLOYEE,
    SUBDIVISION,
    COWORKER
}

dataType Date
operations
    Date(date : String)
end

class AddressBook
end

abstract class Contact
attributes
    name : String
    phone : String
    website : String
    email : String
end

class Note
attributes
    author : String
    time : Date
    type : NoteType
    comment : String
end

class Company < Contact
attributes
    industry : String
end

class Person < Contact
attributes
    title : String
end

class Address
attributes
    city : String
    houseNr : String
    street : String
end

class Relationship
attributes
    type : RelationshipType
end

composition AddressBookMadeOfContact between
    AddressBook[1]
    Contact[*]
end

composition ContactContainsNote between
    Contact[1]
    Note[*]
end

association RelationshipToContact between
    Relationship[*] role isRelated
    Contact[1] role target
end

composition ContactToRelationship between
    Contact[1]
    Relationship[*] role relates
end

composition ContactContainsAddress between
    Contact[1] role source
    Address[*] role address
end


constraints
context Contact inv DifferentSourceTarget:
    self.relates->forAll(r | r.target<>self)
</domain_model>

<object_model>
!new AddressBook('WorldCulinaryNetworkAddressBook')

!new Company('GourmetGroupInc')
!GourmetGroupInc.name := 'Gourmet Group Inc.'
!GourmetGroupInc.phone := '+1-212-555-1020'
!GourmetGroupInc.website := 'www.gourmetgroup.com'
!GourmetGroupInc.email := 'inquiries@gourmetgroup.com'
!GourmetGroupInc.industry := 'Hospitality & Food'

!new Address('GourmetGroupAddress')
!GourmetGroupAddress.city := 'New York'
!GourmetGroupAddress.houseNr := '750'
!GourmetGroupAddress.street := 'Culinary Plaza'
!insert (GourmetGroupInc, GourmetGroupAddress) into ContactContainsAddress

!new Person('ChefPierreDubois')
!ChefPierreDubois.name := 'Chef Pierre Dubois'
!ChefPierreDubois.phone := '+33-1-555-0654'
!ChefPierreDubois.email := 'pierre.dubois@frenchflavor.fr'
!ChefPierreDubois.title := 'Executive Chef'

!new Address('PierreDuboisAddress')
!PierreDuboisAddress.city := 'Paris'
!PierreDuboisAddress.houseNr := '66'
!PierreDuboisAddress.street := 'Rue de la Cuisine'
!insert (ChefPierreDubois, PierreDuboisAddress) into ContactContainsAddress

!new Note('PierreDuboisNote1')
!PierreDuboisNote1.author := 'Gourmet Group Inc.'
!PierreDuboisNote1.time := Date('2023-10-07')
!PierreDuboisNote1.type := #EMAIL
!PierreDuboisNote1.comment := 'Sent invitation to Global Culinary Summit.'
!insert (ChefPierreDubois, PierreDuboisNote1) into ContactContainsNote

!new Company('AsianCulinaryAcademy')
!AsianCulinaryAcademy.name := 'Asian Culinary Academy'
!AsianCulinaryAcademy.phone := '+81-3-5550-2208'
!AsianCulinaryAcademy.website := 'www.asianculinary.ac.jp'
!AsianCulinaryAcademy.email := 'info@asianculinary.ac.jp'
!AsianCulinaryAcademy.industry := 'Education'

!new Person('ChefMariaLopez')
!ChefMariaLopez.name := 'Chef Maria Lopez'
!ChefMariaLopez.phone := '+34-91-555-0423'
!ChefMariaLopez.website := 'www.chefmaria.es'
!ChefMariaLopez.email := 'maria.lopez@innovocuisine.es'
!ChefMariaLopez.title := 'Pastry Chef'

!new Address('MariaLopezAddress1')
!MariaLopezAddress1.city := 'Madrid'
!MariaLopezAddress1.houseNr := '99'
!MariaLopezAddress1.street := 'Dulce Street'
!insert (ChefMariaLopez, MariaLopezAddress1) into ContactContainsAddress

!new Address('MariaLopezAddress2')
!MariaLopezAddress2.city := 'Barcelona'
!MariaLopezAddress2.houseNr := '88'
!MariaLopezAddress2.street := 'Pastelería Avenue'
!insert (ChefMariaLopez, MariaLopezAddress2) into ContactContainsAddress

!new Relationship('GourmetToPierreBoss')
!GourmetToPierreBoss.type := #BOSS
!insert (GourmetToPierreBoss, ChefPierreDubois) into RelationshipToContact
!insert (GourmetGroupInc, GourmetToPierreBoss) into ContactToRelationship

!new Relationship('MariaToAsianCulinaryEmployee')
!MariaToAsianCulinaryEmployee.type := #EMPLOYEE
!insert (MariaToAsianCulinaryEmployee, AsianCulinaryAcademy) into RelationshipToContact
!insert (ChefMariaLopez, MariaToAsianCulinaryEmployee) into ContactToRelationship

!new Relationship('PierreToMariaCoworker')
!PierreToMariaCoworker.type := #COWORKER
!insert (PierreToMariaCoworker, ChefMariaLopez) into RelationshipToContact
!insert (ChefPierreDubois, PierreToMariaCoworker) into ContactToRelationship

!insert (WorldCulinaryNetworkAddressBook, GourmetGroupInc) into AddressBookMadeOfContact
!insert (WorldCulinaryNetworkAddressBook, ChefPierreDubois) into AddressBookMadeOfContact
!insert (WorldCulinaryNetworkAddressBook, AsianCulinaryAcademy) into AddressBookMadeOfContact
!insert (WorldCulinaryNetworkAddressBook, ChefMariaLopez) into AddressBookMadeOfContact
</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>

For the same category and model description, generate another instance that is structurally and semantically different from the previous ones

Continue with the following description, creating the instance according to the syntax example and this specification: 
## Complex Address Book Instance

### Address Book: "Global Education Network"

The "Global Education Network" address book encompasses a variety of academic and educational institutions as well as individual educators, highlighting collaborations within the international education sector.

#### Contacts

1. **Contact 1 - Person**
   - **Name**: Prof. Elena Martinez
   - **Phone**: +34 91 3344 9988
   - **Website**: www.elenamartinez.academia.es
   - **Email**: elena.martinez@univ.es
   - **Title**: Dean of Social Sciences

   - **Addresses**:
     - **1.1 Address**:
       - **City**: Madrid
       - **Street**: Knowledge Lane
       - **House Number**: 101

   - **Notes**:
     - **1.1 Note**:
       - **Author**: Prof. Elena Martinez
       - **Time**: "2023-05-12"
       - **Type**: MEETING
       - **Comment**: "Led panel on the impacts of globalization on education systems worldwide."

     - **1.2 Note**:
       - **Author**: Prof. Elena Martinez
       - **Time**: "2023-05-20"
       - **Type**: EMAIL
       - **Comment**: "Sent a strategic proposal for a new international student exchange program."

   - **Relationships**:
     - **1.1 Relationship** to Contact 3:
       - **Type**: EMPLOYEE

2. **Contact 2 - Person**
   - **Name**: Dr. Nia Hadjari
   - **Phone**: +231 445 8876
   - **Website**: www.niahadjari.org
   - **Email**: nhadjari@minedu.gov.lr
   - **Title**: Educational Policy Advisor

   - **Addresses**:
     - **2.1 Address**:
       - **City**: Monrovia
       - **Street**: Policy Drive
       - **House Number**: 12

   - **Notes**:
     - **2.1 Note**:
       - **Author**: Dr. Nia Hadjari
       - **Time**: "2023-06-07"
       - **Type**: CALL
       - **Comment**: "Phone call with EU representatives regarding educational initiatives."

   - **Relationships**:
     - **2.1 Relationship** to Contact 4:
       - **Type**: EMPLOYEE

3. **Contact 3 - Company**
   - **Name**: Education for All Foundation
   - **Phone**: +44 20 4455 6677
   - **Website**: www.educationforall.org
   - **Email**: info@educationforall.org
   - **Industry**: Non-Profit Education

   - **Addresses**:
     - **3.1 Address**:
       - **City**: London
       - **Street**: Equity Street
       - **House Number**: 50

   - **Notes**:
     - **3.1 Note**:
       - **Author**: Education for All Foundation
       - **Time**: "2023-07-10"
       - **Type**: MEETING
       - **Comment**: "Hosted annual summit on educational access and equity."

   - **Relationships**:
     - **3.1 Relationship** to Contact 1:
       - **Type**: BOSS

4. **Contact 4 - Company**
   - **Name**: Global Learning Initiative
   - **Phone**: +1 212 567 8901
   - **Website**: www.globallearninginitiative.org
   - **Email**: admin@globallearning.org
   - **Industry**: Educational Consulting

   - **Addresses**:
     - **4.1 Address**:
       - **City**: New York
       - **Street**: Learning Avenue
       - **House Number**: 88

   - **Notes**:
     - **4.1 Note**:
       - **Author**: Global Learning Initiative
       - **Time**: "2023-07-25"
       - **Type**: EMAIL
       - **Comment**: "Announced new funding opportunities for collaborative educational projects."

   - **Relationships**:
     - **4.1 Relationship** to Contact 2:
       - **Type**: BOSS
     - **4.2 Relationship** to Contact 3:
       - **Type**: SUBDIVISION

### Invariant Check
- **DifferentSourceTarget**: Verified all relationship targets differ from their sources, ensuring no self-referential errors occur.

This instance presents a broad spectrum of educational entities and figures, demonstrating cross-cultural and cross-continental collaborations aimed at advancing global educational practices.

<domain_model>
model AddressBook

enum NoteType {
    MEETING,
    CALL,
    EMAIL
}

enum RelationshipType {
    BOSS,
    EMPLOYEE,
    SUBDIVISION,
    COWORKER
}

dataType Date
operations
    Date(date : String)
end

class AddressBook
end

abstract class Contact
attributes
    name : String
    phone : String
    website : String
    email : String
end

class Note
attributes
    author : String
    time : Date
    type : NoteType
    comment : String
end

class Company < Contact
attributes
    industry : String
end

class Person < Contact
attributes
    title : String
end

class Address
attributes
    city : String
    houseNr : String
    street : String
end

class Relationship
attributes
    type : RelationshipType
end

composition AddressBookMadeOfContact between
    AddressBook[1]
    Contact[*]
end

composition ContactContainsNote between
    Contact[1]
    Note[*]
end

association RelationshipToContact between
    Relationship[*] role isRelated
    Contact[1] role target
end

composition ContactToRelationship between
    Contact[1]
    Relationship[*] role relates
end

composition ContactContainsAddress between
    Contact[1] role source
    Address[*] role address
end


constraints
context Contact inv DifferentSourceTarget:
    self.relates->forAll(r | r.target<>self)
</domain_model>

<object_model>
!new AddressBook('GlobalEducationNetwork')

!new Person('ProfElenaMartinez')
!ProfElenaMartinez.name := 'Prof. Elena Martinez'
!ProfElenaMartinez.phone := '+34 91 3344 9988'
!ProfElenaMartinez.website := 'www.elenamartinez.academia.es'
!ProfElenaMartinez.email := 'elena.martinez@univ.es'
!ProfElenaMartinez.title := 'Dean of Social Sciences'

!new Address('ElenaMartinezAddress')
!ElenaMartinezAddress.city := 'Madrid'
!ElenaMartinezAddress.street := 'Knowledge Lane'
!ElenaMartinezAddress.houseNr := '101'
!insert (ProfElenaMartinez, ElenaMartinezAddress) into ContactContainsAddress

!new Note('ElenaMartinezNote1')
!ElenaMartinezNote1.author := 'Prof. Elena Martinez'
!ElenaMartinezNote1.time := Date('2023-05-12')
!ElenaMartinezNote1.type := #MEETING
!ElenaMartinezNote1.comment := 'Led panel on the impacts of globalization on education systems worldwide.'
!insert (ProfElenaMartinez, ElenaMartinezNote1) into ContactContainsNote

!new Note('ElenaMartinezNote2')
!ElenaMartinezNote2.author := 'Prof. Elena Martinez'
!ElenaMartinezNote2.time := Date('2023-05-20')
!ElenaMartinezNote2.type := #EMAIL
!ElenaMartinezNote2.comment := 'Sent a strategic proposal for a new international student exchange program.'
!insert (ProfElenaMartinez, ElenaMartinezNote2) into ContactContainsNote

!new Person('DrNiaHadjari')
!DrNiaHadjari.name := 'Dr. Nia Hadjari'
!DrNiaHadjari.phone := '+231 445 8876'
!DrNiaHadjari.website := 'www.niahadjari.org'
!DrNiaHadjari.email := 'nhadjari@minedu.gov.lr'
!DrNiaHadjari.title := 'Educational Policy Advisor'

!new Address('NiaHadjariAddress')
!NiaHadjariAddress.city := 'Monrovia'
!NiaHadjariAddress.street := 'Policy Drive'
!NiaHadjariAddress.houseNr := '12'
!insert (DrNiaHadjari, NiaHadjariAddress) into ContactContainsAddress

!new Note('NiaHadjariNote')
!NiaHadjariNote.author := 'Dr. Nia Hadjari'
!NiaHadjariNote.time := Date('2023-06-07')
!NiaHadjariNote.type := #CALL
!NiaHadjariNote.comment := 'Phone call with EU representatives regarding educational initiatives.'
!insert (DrNiaHadjari, NiaHadjariNote) into ContactContainsNote

!new Company('EducationForAllFoundation')
!EducationForAllFoundation.name := 'Education for All Foundation'
!EducationForAllFoundation.phone := '+44 20 4455 6677'
!EducationForAllFoundation.website := 'www.educationforall.org'
!EducationForAllFoundation.email := 'info@educationforall.org'
!EducationForAllFoundation.industry := 'Non-Profit Education'

!new Address('EducationForAllAddress')
!EducationForAllAddress.city := 'London'
!EducationForAllAddress.street := 'Equity Street'
!EducationForAllAddress.houseNr := '50'
!insert (EducationForAllFoundation, EducationForAllAddress) into ContactContainsAddress

!new Note('EducationForAllNote')
!EducationForAllNote.author := 'Education for All Foundation'
!EducationForAllNote.time := Date('2023-07-10')
!EducationForAllNote.type := #MEETING
!EducationForAllNote.comment := 'Hosted annual summit on educational access and equity.'
!insert (EducationForAllFoundation, EducationForAllNote) into ContactContainsNote

!new Company('GlobalLearningInitiative')
!GlobalLearningInitiative.name := 'Global Learning Initiative'
!GlobalLearningInitiative.phone := '+1 212 567 8901'
!GlobalLearningInitiative.website := 'www.globallearninginitiative.org'
!GlobalLearningInitiative.email := 'admin@globallearning.org'
!GlobalLearningInitiative.industry := 'Educational Consulting'

!new Address('GlobalLearningAddress')
!GlobalLearningAddress.city := 'New York'
!GlobalLearningAddress.street := 'Learning Avenue'
!GlobalLearningAddress.houseNr := '88'
!insert (GlobalLearningInitiative, GlobalLearningAddress) into ContactContainsAddress

!new Note('GlobalLearningNote')
!GlobalLearningNote.author := 'Global Learning Initiative'
!GlobalLearningNote.time := Date('2023-07-25')
!GlobalLearningNote.type := #EMAIL
!GlobalLearningNote.comment := 'Announced new funding opportunities for collaborative educational projects.'
!insert (GlobalLearningInitiative, GlobalLearningNote) into ContactContainsNote

!new Relationship('ElenaToEducationForAllEmployee')
!ElenaToEducationForAllEmployee.type := #EMPLOYEE
!insert (ElenaToEducationForAllEmployee, EducationForAllFoundation) into RelationshipToContact
!insert (ProfElenaMartinez, ElenaToEducationForAllEmployee) into ContactToRelationship

!new Relationship('NiaToGlobalLearningEmployee')
!NiaToGlobalLearningEmployee.type := #EMPLOYEE
!insert (NiaToGlobalLearningEmployee, GlobalLearningInitiative) into RelationshipToContact
!insert (DrNiaHadjari, NiaToGlobalLearningEmployee) into ContactToRelationship

!new Relationship('EducationForAllToElenaBoss')
!EducationForAllToElenaBoss.type := #BOSS
!insert (EducationForAllToElenaBoss, ProfElenaMartinez) into RelationshipToContact
!insert (EducationForAllFoundation, EducationForAllToElenaBoss) into ContactToRelationship

!new Relationship('GlobalLearningToNiaBoss')
!GlobalLearningToNiaBoss.type := #BOSS
!insert (GlobalLearningToNiaBoss, DrNiaHadjari) into RelationshipToContact
!insert (GlobalLearningInitiative, GlobalLearningToNiaBoss) into ContactToRelationship

!new Relationship('GlobalLearningToEducationForAllSubdivision')
!GlobalLearningToEducationForAllSubdivision.type := #SUBDIVISION
!insert (GlobalLearningToEducationForAllSubdivision, EducationForAllFoundation) into RelationshipToContact
!insert (GlobalLearningInitiative, GlobalLearningToEducationForAllSubdivision) into ContactToRelationship

!insert (GlobalEducationNetwork, ProfElenaMartinez) into AddressBookMadeOfContact
!insert (GlobalEducationNetwork, DrNiaHadjari) into AddressBookMadeOfContact
!insert (GlobalEducationNetwork, EducationForAllFoundation) into AddressBookMadeOfContact
!insert (GlobalEducationNetwork, GlobalLearningInitiative) into AddressBookMadeOfContact
</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>

For the same category and model description, generate another instance that is structurally and semantically different from the previous ones

Continue with the following description, creating the instance according to the syntax example and this specification: 
In this edge case instance, the address book is constructed for managing an intricate network of a multinational media conglomerate with connections crossing major players in different media sectors. The instance includes highly complex relationships among companies and individuals, marking distinct hierarchical and collaborative roles within the entertainment and publishing industries.

### Address Book Instance
- **AddressBook: Media and Entertainment Network**

### Contacts
1. **Contact (Company)**
   - **Name**: Luna Productions
   - **Phone**: +1-310-7771234
   - **Website**: www.lunaproductions.us
   - **Email**: contact@lunaproductions.us
   - **Industry**: Film Production
   - **Notes**:
     - **Note 1**:
       - **Author**: Evelyn Hart
       - **Time**: "2023-09-15T10:00:00"
       - **Type**: MEETING
       - **Comment**: Annual planning session held in Los Angeles.
   - **Address**:
     - **City**: Los Angeles
     - **HouseNr**: 500
     - **Street**: Hollywood Boulevard
   - **Relationships**:
     - **To**: Maxwell Chen (Relation: COWORKER)
     - **To**: Brighter Days Publishing (Relation: SUBDIVISION)

2. **Contact (Company)**
   - **Name**: Brighter Days Publishing
   - **Phone**: +44-20-76191122
   - **Website**: www.brighterdayspub.co.uk
   - **Email**: editor@brighterdayspub.co.uk
   - **Industry**: Publishing
   - **Notes**:
     - **Note 1**:
       - **Author**: Jonathan Price
       - **Time**: "2023-06-22T08:30:00"
       - **Type**: EMAIL
       - **Comment**: Draft collaboration agreement with Luna Productions.
   - **Address**:
     - **City**: London
     - **HouseNr**: 120
     - **Street**: Print Press Way
   - **Relationships**:
     - **To**: Luna Productions (Relation: BOSS)
     - **To**: Maxwell Chen (Relation: EMPLOYEE)

3. **Contact (Person)**
   - **Name**: Maxwell Chen
   - **Phone**: +86-10-88765432
   - **Website**: www.maxwellchenmedia.cn
   - **Email**: m.chen@media.cn
   - **Title**: Media Strategist
   - **Notes**:
     - **Note 1**:
       - **Author**: Maxwell Chen
       - **Time**: "2023-08-30T18:00:00"
       - **Type**: CALL
       - **Comment**: Discussed expanding media research in Asian markets.
     - **Note 2**:
       - **Author**: Maxwell Chen
       - **Time**: "2023-07-04T14:00:00"
       - **Type**: MEETING
       - **Comment**: Strategy meeting with multiple divisions in Beijing.
   - **Address**:
     - **City**: Beijing
     - **HouseNr**: 18
     - **Street**: Media Hub Road
   - **Relationships**:
     - **To**: Brighter Days Publishing (Relation: EMPLOYEE)

4. **Contact (Company)**
   - **Name**: StarSound Studios
   - **Phone**: +91-80-66554433
   - **Website**: www.starsoundstudios.in
   - **Email**: info@starsoundstudios.in
   - **Industry**: Music Production
   - **Notes**:
     - **Note 1**:
       - **Author**: Priya Menon
       - **Time**: "2023-05-10T11:30:00"
       - **Type**: CALL
       - **Comment**: Meeting with investors on the upcoming music festival.
   - **Address**:
     - **City**: Bangalore
     - **HouseNr**: 33
     - **Street**: Melody Lane
   - **Relationships**:
     - **To**: Maxwell Chen (Relation: COWORKER)

### Edge Case Details
- **Industrially Diverse Contacts**: The instance showcases significant players in distinct branches of media, including film, music, and publishing, illustrating a comprehensive media conglomerate scenario.
- **Complex Hierarchies**: Consists of cross-industrial hierarchy where Brighter Days Publishing acts as a large entity's subdivision while also having managerial roles.
- **Multinational Presence**: The scenario spans several key global cities in media, from LA to London, Beijing to Bangalore, highlighting geographic diversity in operations.
- **Intricate Networks**: Maxwell Chen operates as a pivotal node bridging creative and strategic components across entities, signifying the strategic connections within the conglomerate's network.
- **Unusual Relationships**: Integrates unique interplay between traditionally independent industries within a singular collaborative and competitive framework.

<domain_model>
model AddressBook

enum NoteType {
    MEETING,
    CALL,
    EMAIL
}

enum RelationshipType {
    BOSS,
    EMPLOYEE,
    SUBDIVISION,
    COWORKER
}

dataType Date
operations
    Date(date : String)
end

class AddressBook
end

abstract class Contact
attributes
    name : String
    phone : String
    website : String
    email : String
end

class Note
attributes
    author : String
    time : Date
    type : NoteType
    comment : String
end

class Company < Contact
attributes
    industry : String
end

class Person < Contact
attributes
    title : String
end

class Address
attributes
    city : String
    houseNr : String
    street : String
end

class Relationship
attributes
    type : RelationshipType
end

composition AddressBookMadeOfContact between
    AddressBook[1]
    Contact[*]
end

composition ContactContainsNote between
    Contact[1]
    Note[*]
end

association RelationshipToContact between
    Relationship[*] role isRelated
    Contact[1] role target
end

composition ContactToRelationship between
    Contact[1]
    Relationship[*] role relates
end

composition ContactContainsAddress between
    Contact[1] role source
    Address[*] role address
end


constraints
context Contact inv DifferentSourceTarget:
    self.relates->forAll(r | r.target<>self)
</domain_model>

<object_model>
!new AddressBook('MediaAndEntertainmentNetwork')

!new Company('LunaProductions')
!LunaProductions.name := 'Luna Productions'
!LunaProductions.phone := '+1-310-7771234'
!LunaProductions.website := 'www.lunaproductions.us'
!LunaProductions.email := 'contact@lunaproductions.us'
!LunaProductions.industry := 'Film Production'

!new Address('LunaProductionsAddress')
!LunaProductionsAddress.city := 'Los Angeles'
!LunaProductionsAddress.houseNr := '500'
!LunaProductionsAddress.street := 'Hollywood Boulevard'
!insert (LunaProductions, LunaProductionsAddress) into ContactContainsAddress

!new Note('LunaProductionsNote1')
!LunaProductionsNote1.author := 'Evelyn Hart'
!LunaProductionsNote1.time := Date('2023-09-15T10:00:00')
!LunaProductionsNote1.type := #MEETING
!LunaProductionsNote1.comment := 'Annual planning session held in Los Angeles.'
!insert (LunaProductions, LunaProductionsNote1) into ContactContainsNote

!new Company('BrighterDaysPublishing')
!BrighterDaysPublishing.name := 'Brighter Days Publishing'
!BrighterDaysPublishing.phone := '+44-20-76191122'
!BrighterDaysPublishing.website := 'www.brighterdayspub.co.uk'
!BrighterDaysPublishing.email := 'editor@brighterdayspub.co.uk'
!BrighterDaysPublishing.industry := 'Publishing'

!new Address('BrighterDaysAddress')
!BrighterDaysAddress.city := 'London'
!BrighterDaysAddress.houseNr := '120'
!BrighterDaysAddress.street := 'Print Press Way'
!insert (BrighterDaysPublishing, BrighterDaysAddress) into ContactContainsAddress

!new Note('BrighterDaysNote1')
!BrighterDaysNote1.author := 'Jonathan Price'
!BrighterDaysNote1.time := Date('2023-06-22T08:30:00')
!BrighterDaysNote1.type := #EMAIL
!BrighterDaysNote1.comment := 'Draft collaboration agreement with Luna Productions.'
!insert (BrighterDaysPublishing, BrighterDaysNote1) into ContactContainsNote

!new Person('MaxwellChen')
!MaxwellChen.name := 'Maxwell Chen'
!MaxwellChen.phone := '+86-10-88765432'
!MaxwellChen.website := 'www.maxwellchenmedia.cn'
!MaxwellChen.email := 'm.chen@media.cn'
!MaxwellChen.title := 'Media Strategist'

!new Address('MaxwellChenAddress')
!MaxwellChenAddress.city := 'Beijing'
!MaxwellChenAddress.houseNr := '18'
!MaxwellChenAddress.street := 'Media Hub Road'
!insert (MaxwellChen, MaxwellChenAddress) into ContactContainsAddress

!new Note('MaxwellChenNote1')
!MaxwellChenNote1.author := 'Maxwell Chen'
!MaxwellChenNote1.time := Date('2023-08-30T18:00:00')
!MaxwellChenNote1.type := #CALL
!MaxwellChenNote1.comment := 'Discussed expanding media research in Asian markets.'
!insert (MaxwellChen, MaxwellChenNote1) into ContactContainsNote

!new Note('MaxwellChenNote2')
!MaxwellChenNote2.author := 'Maxwell Chen'
!MaxwellChenNote2.time := Date('2023-07-04T14:00:00')
!MaxwellChenNote2.type := #MEETING
!MaxwellChenNote2.comment := 'Strategy meeting with multiple divisions in Beijing.'
!insert (MaxwellChen, MaxwellChenNote2) into ContactContainsNote

!new Company('StarSoundStudios')
!StarSoundStudios.name := 'StarSound Studios'
!StarSoundStudios.phone := '+91-80-66554433'
!StarSoundStudios.website := 'www.starsoundstudios.in'
!StarSoundStudios.email := 'info@starsoundstudios.in'
!StarSoundStudios.industry := 'Music Production'

!new Address('StarSoundAddress')
!StarSoundAddress.city := 'Bangalore'
!StarSoundAddress.houseNr := '33'
!StarSoundAddress.street := 'Melody Lane'
!insert (StarSoundStudios, StarSoundAddress) into ContactContainsAddress

!new Note('StarSoundNote1')
!StarSoundNote1.author := 'Priya Menon'
!StarSoundNote1.time := Date('2023-05-10T11:30:00')
!StarSoundNote1.type := #CALL
!StarSoundNote1.comment := 'Meeting with investors on the upcoming music festival.'
!insert (StarSoundStudios, StarSoundNote1) into ContactContainsNote

!new Relationship('LunaToMaxwellCoworker')
!LunaToMaxwellCoworker.type := #COWORKER
!insert (LunaToMaxwellCoworker, MaxwellChen) into RelationshipToContact
!insert (LunaProductions, LunaToMaxwellCoworker) into ContactToRelationship

!new Relationship('LunaToBrighterDaysSubdivision')
!LunaToBrighterDaysSubdivision.type := #SUBDIVISION
!insert (LunaToBrighterDaysSubdivision, BrighterDaysPublishing) into RelationshipToContact
!insert (LunaProductions, LunaToBrighterDaysSubdivision) into ContactToRelationship

!new Relationship('BrighterDaysToLunaBoss')
!BrighterDaysToLunaBoss.type := #BOSS
!insert (BrighterDaysToLunaBoss, LunaProductions) into RelationshipToContact
!insert (BrighterDaysPublishing, BrighterDaysToLunaBoss) into ContactToRelationship

!new Relationship('BrighterDaysToMaxwellEmployee')
!BrighterDaysToMaxwellEmployee.type := #EMPLOYEE
!insert (BrighterDaysToMaxwellEmployee, MaxwellChen) into RelationshipToContact
!insert (BrighterDaysPublishing, BrighterDaysToMaxwellEmployee) into ContactToRelationship

!new Relationship('StarSoundToMaxwellCoworker')
!StarSoundToMaxwellCoworker.type := #COWORKER
!insert (StarSoundToMaxwellCoworker, MaxwellChen) into RelationshipToContact
!insert (StarSoundStudios, StarSoundToMaxwellCoworker) into ContactToRelationship

!insert (MediaAndEntertainmentNetwork, LunaProductions) into AddressBookMadeOfContact
!insert (MediaAndEntertainmentNetwork, BrighterDaysPublishing) into AddressBookMadeOfContact
!insert (MediaAndEntertainmentNetwork, MaxwellChen) into AddressBookMadeOfContact
!insert (MediaAndEntertainmentNetwork, StarSoundStudios) into AddressBookMadeOfContact
</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>

For the same category and model description, generate another instance that is structurally and semantically different from the previous ones

Continue with the following description, creating the instance according to the syntax example and this specification: 
## Overconstraint Detection Instance

### Scenario Overview
This instance involves a global culinary event organization where multiple chefs and culinary institutes collaborate for an international food festival. This instance will highlight potential overconstraints concerning relationships and the rich variety of notes needed to track interactions, scheduling, and cultural exchanges.

### Instance Description

1. **AddressBook**
   - **Culinary Festival Address Book**: Contains contacts of all participants and organizers involved in the Global Food Festival.

2. **Contacts**
   - **Culinary Institute (International Culinary Academy)**:
     - **Industry**: Education
     - **Phone**: +1-213-555-0280
     - **Website**: www.iculinaryacademy.org
     - **Email**: info@iculinaryacademy.org
     - **Addresses**:
       - **Address 1**: 
         - City: Los Angeles
         - HouseNr: 356
         - Street: Gastronomy Blvd
     - **Relationships**: 
       - **Chef Maria**: EMPLOYEE (TARGET: Chef Maria)
       - **Chef Antoine**: SUBDIVISION (TARGET: Chef Antoine)

   - **Chef Maria (Maria del Sol)**:
     - **Title**: Head Chef
     - **Phone**: +34-655-555123
     - **Email**: maria.delsol@chefcuisine.es
     - **Addresses**:
       - **Address 1**:
         - City: Barcelona
         - HouseNr: 18
         - Street: Chef Street
     - **Relationships**:
       - **Chef Antoine**: COWORKER (TARGET: Chef Antoine)
       - **Event Organizer**: COWORKER (TARGET: Event Organizer)

   - **Chef Antoine (Antoine Dubois)**:
     - **Title**: Pastry Chef
     - **Phone**: +33-1-5557532
     - **Email**: antoine.dubois@frenchdelights.fr
     - **Addresses**:
       - **Address 1**:
         - City: Paris
         - HouseNr: 24
         - Street: Desserts Alley
     - **Relationships**:
       - **Culinary Institute**: EMPLOYEE (TARGET: Culinary Institute)

   - **Event Organizer (Sophia Tran)**:
     - **Industry**: Event Management
     - **Phone**: +61-3-5552377
     - **Email**: sophia.tran@culinaryevents.com
     - **Addresses**:
       - **Address 1**:
         - City: Melbourne
         - HouseNr: 200
         - Street: Event Drive

3. **Notes**
   - **Note for Culinary Institute**:
     - **Author**: Festival Director
     - **Time**: 2023-06-10
     - **Type**: EMAIL
     - **Comment**: Confirm participation in the international food festival.
   - **Note for Chef Maria**:
     - **Author**: Chef Maria
     - **Time**: 2023-05-12
     - **Type**: MEETING
     - **Comment**: Coordinate Mediterranean cuisine showcase plan.
   - **Note for Chef Antoine**: (Unusually frequent and complex note interaction)
     - **Author**: Patissier's Network
     - **Time**: 2023-05-14
     - **Type**: CALL
     - **Comment**: Discuss the arrangement for the multi-national dessert tasting.

### Overconstraint Analysis

- **Violation**: The model constraints are restrictive in terms of the allowable relationships and notes. This instance illustrates the complexity of interactions expected at a culinary event: for example, Chef Maria works closely with the event organizer and Culinary Institute but has a coworker relationship with Chef Antoine that could benefit from more expressive relationship types to capture the richness of festival preparations. Additionally, limiting notes to one per type overlooks the depth of planning discussions, recipe trials, and logistical updates that need to be tracked.

- **Insight**: To support diverse and intensive communication and role management in global culinary collaborations, the model should accommodate multiple, overlapping relationships among contacts to handle the myriad participatory roles. Likewise, enhancements in note handling to reflect real-world complexities such as more dynamic interactions, frequent updates, and varying levels of collaboration would significantly improve the system's usability in handling international, multi-faceted events.

<domain_model>
model AddressBook

enum NoteType {
    MEETING,
    CALL,
    EMAIL
}

enum RelationshipType {
    BOSS,
    EMPLOYEE,
    SUBDIVISION,
    COWORKER
}

dataType Date
operations
    Date(date : String)
end

class AddressBook
end

abstract class Contact
attributes
    name : String
    phone : String
    website : String
    email : String
end

class Note
attributes
    author : String
    time : Date
    type : NoteType
    comment : String
end

class Company < Contact
attributes
    industry : String
end

class Person < Contact
attributes
    title : String
end

class Address
attributes
    city : String
    houseNr : String
    street : String
end

class Relationship
attributes
    type : RelationshipType
end

composition AddressBookMadeOfContact between
    AddressBook[1]
    Contact[*]
end

composition ContactContainsNote between
    Contact[1]
    Note[*]
end

association RelationshipToContact between
    Relationship[*] role isRelated
    Contact[1] role target
end

composition ContactToRelationship between
    Contact[1]
    Relationship[*] role relates
end

composition ContactContainsAddress between
    Contact[1] role source
    Address[*] role address
end


constraints
context Contact inv DifferentSourceTarget:
    self.relates->forAll(r | r.target<>self)
</domain_model>

<object_model>
!new AddressBook('CulinaryFestivalAddressBook')

!new Company('InternationalCulinaryAcademy')
!InternationalCulinaryAcademy.name := 'International Culinary Academy'
!InternationalCulinaryAcademy.phone := '+1-213-555-0280'
!InternationalCulinaryAcademy.website := 'www.iculinaryacademy.org'
!InternationalCulinaryAcademy.email := 'info@iculinaryacademy.org'
!InternationalCulinaryAcademy.industry := 'Education'

!new Address('CulinaryAcademyAddress')
!CulinaryAcademyAddress.city := 'Los Angeles'
!CulinaryAcademyAddress.houseNr := '356'
!CulinaryAcademyAddress.street := 'Gastronomy Blvd'
!insert (InternationalCulinaryAcademy, CulinaryAcademyAddress) into ContactContainsAddress

!new Note('CulinaryAcademyNote1')
!CulinaryAcademyNote1.author := 'Festival Director'
!CulinaryAcademyNote1.time := Date('2023-06-10')
!CulinaryAcademyNote1.type := #EMAIL
!CulinaryAcademyNote1.comment := 'Confirm participation in the international food festival.'
!insert (InternationalCulinaryAcademy, CulinaryAcademyNote1) into ContactContainsNote

!new Person('ChefMaria')
!ChefMaria.name := 'Maria del Sol'
!ChefMaria.phone := '+34-655-555123'
!ChefMaria.email := 'maria.delsol@chefcuisine.es'
!ChefMaria.title := 'Head Chef'

!new Address('MariaDelSolAddress')
!MariaDelSolAddress.city := 'Barcelona'
!MariaDelSolAddress.houseNr := '18'
!MariaDelSolAddress.street := 'Chef Street'
!insert (ChefMaria, MariaDelSolAddress) into ContactContainsAddress

!new Note('ChefMariaNote1')
!ChefMariaNote1.author := 'Chef Maria'
!ChefMariaNote1.time := Date('2023-05-12')
!ChefMariaNote1.type := #MEETING
!ChefMariaNote1.comment := 'Coordinate Mediterranean cuisine showcase plan.'
!insert (ChefMaria, ChefMariaNote1) into ContactContainsNote

!new Person('ChefAntoine')
!ChefAntoine.name := 'Antoine Dubois'
!ChefAntoine.phone := '+33-1-5557532'
!ChefAntoine.email := 'antoine.dubois@frenchdelights.fr'
!ChefAntoine.title := 'Pastry Chef'

!new Address('AntoineDuboisAddress')
!AntoineDuboisAddress.city := 'Paris'
!AntoineDuboisAddress.houseNr := '24'
!AntoineDuboisAddress.street := 'Desserts Alley'
!insert (ChefAntoine, AntoineDuboisAddress) into ContactContainsAddress

!new Note('ChefAntoineNote1')
!ChefAntoineNote1.author := 'Patissier\'s Network'
!ChefAntoineNote1.time := Date('2023-05-14')
!ChefAntoineNote1.type := #CALL
!ChefAntoineNote1.comment := 'Discuss the arrangement for the multi-national dessert tasting.'
!insert (ChefAntoine, ChefAntoineNote1) into ContactContainsNote

!new Person('SophiaTran')
!SophiaTran.name := 'Sophia Tran'
!SophiaTran.phone := '+61-3-5552377'
!SophiaTran.email := 'sophia.tran@culinaryevents.com'
!SophiaTran.title := 'Event Organizer'

!new Address('SophiaTranAddress')
!SophiaTranAddress.city := 'Melbourne'
!SophiaTranAddress.houseNr := '200'
!SophiaTranAddress.street := 'Event Drive'
!insert (SophiaTran, SophiaTranAddress) into ContactContainsAddress

!new Relationship('CulinaryAcademyToMariaEmployee')
!CulinaryAcademyToMariaEmployee.type := #EMPLOYEE
!insert (CulinaryAcademyToMariaEmployee, ChefMaria) into RelationshipToContact
!insert (InternationalCulinaryAcademy, CulinaryAcademyToMariaEmployee) into ContactToRelationship

!new Relationship('CulinaryAcademyToAntoineSubdivision')
!CulinaryAcademyToAntoineSubdivision.type := #SUBDIVISION
!insert (CulinaryAcademyToAntoineSubdivision, ChefAntoine) into RelationshipToContact
!insert (InternationalCulinaryAcademy, CulinaryAcademyToAntoineSubdivision) into ContactToRelationship

!new Relationship('MariaToAntoineCoworker')
!MariaToAntoineCoworker.type := #COWORKER
!insert (MariaToAntoineCoworker, ChefAntoine) into RelationshipToContact
!insert (ChefMaria, MariaToAntoineCoworker) into ContactToRelationship

!new Relationship('MariaToSophiaCoworker')
!MariaToSophiaCoworker.type := #COWORKER
!insert (MariaToSophiaCoworker, SophiaTran) into RelationshipToContact
!insert (ChefMaria, MariaToSophiaCoworker) into ContactToRelationship

!new Relationship('AntoineToCulinaryAcademyEmployee')
!AntoineToCulinaryAcademyEmployee.type := #EMPLOYEE
!insert (AntoineToCulinaryAcademyEmployee, InternationalCulinaryAcademy) into RelationshipToContact
!insert (ChefAntoine, AntoineToCulinaryAcademyEmployee) into ContactToRelationship

!insert (CulinaryFestivalAddressBook, InternationalCulinaryAcademy) into AddressBookMadeOfContact
!insert (CulinaryFestivalAddressBook, ChefMaria) into AddressBookMadeOfContact
!insert (CulinaryFestivalAddressBook, ChefAntoine) into AddressBookMadeOfContact
!insert (CulinaryFestivalAddressBook, SophiaTran) into AddressBookMadeOfContact
</object_model>