AddressBook / gen4

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: International Professional Network

### Address Book
- **Name**: International Professional Network

### Contacts

#### 1. Person Contact
- **Name**: Carlos Mendes
- **Phone**: +351-21-998-7654
- **Website**: www.carlosmendes.pt
- **Email**: carlos.mendes@marketingportugal.pt
- **Title**: Chief Marketing Officer

##### Notes for Carlos Mendes
1. **Note**
   - **Author**: Carlos Mendes
   - **Time**: "2023-02-10"
   - **Type**: EMAIL
   - **Comment**: Overview of strategic marketing initiatives for Q2.

##### Address for Carlos Mendes
- **City**: Lisbon
- **House Number**: 45
- **Street**: Rua Augusta

##### Relationships for Carlos Mendes
1. **Relationship**
   - **Type**: BOSS
   - **Target**: Paolo Conti

2. **Relationship**
   - **Type**: COWORKER
   - **Target**: Jean Baptiste

#### 2. Company Contact
- **Name**: Eco Energy Systems
- **Phone**: +49-89-1234-5678
- **Website**: www.ecoenergysystems.de
- **Email**: info@ecoenergysystems.de
- **Industry**: Renewable Energy

##### Notes for Eco Energy Systems
- **Note**
  - **Author**: Hans Müller
  - **Time**: "2023-05-25"
  - **Type**: MEETING
  - **Comment**: Discussion about expanding solar energy projects in Southern Europe.

##### Address for Eco Energy Systems
- **City**: Munich
- **House Number**: 30
- **Street**: Sonnenstraße

#### 3. Person Contact
- **Name**: Paolo Conti
- **Phone**: +39-06-4444-5555
- **Website**: www.paoloconticonsulting.it
- **Email**: paolo.conti@innovationitalia.it
- **Title**: Innovation Consultant

##### Notes for Paolo Conti
- **Note**
  - **Author**: Paolo Conti
  - **Time**: "2023-04-18"
  - **Type**: CALL
  - **Comment**: Insights on integrating AI into customer service.

##### Address for Paolo Conti
- **City**: Rome
- **House Number**: 22
- **Street**: Via Condotti

##### Relationships for Paolo Conti
- **Relationship**
  - **Type**: EMPLOYEE
  - **Target**: Carlos Mendes

#### 4. Person Contact
- **Name**: Jean Baptiste
- **Phone**: +33-1-7543-2109
- **Website**: www.jeanbaptiste.fr
- **Email**: jean.baptiste@entrepreneurfrance.fr
- **Title**: Entrepreneur

##### Notes for Jean Baptiste
- **Note**
  - **Author**: Jean Baptiste
  - **Time**: "2023-03-30"
  - **Type**: EMAIL
  - **Comment**: Proposal for joint ventures in sustainable agriculture.

##### Address for Jean Baptiste
- **City**: Paris
- **House Number**: 12
- **Street**: Champs-Élysées

##### Relationships for Jean Baptiste
1. **Relationship**
   - **Type**: COWORKER
   - **Target**: Carlos Mendes

2. **Relationship**
   - **Type**: SUBDIVISION
   - **Target**: Eco Energy Systems

### Relationships

- **Carlos Mendes** manages **Paolo Conti** and is his **BOSS**.
- **Paolo Conti** reports directly to **Carlos Mendes** as an **EMPLOYEE**.
- **Carlos Mendes** and **Jean Baptiste** work as **COWORKERS**.
- **Jean Baptiste** collaborates with **Eco Energy Systems** as a **SUBDIVISION** where he leads certain projects.

This instance emphasizes international cooperation between individuals and companies within Europe, focusing on renewable energy, marketing innovations, and entrepreneurship. It demonstrates different professional roles and affiliations set in distinct regions and highlights dynamic interactions across multiple sectors.

<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('InternationalProfessionalNetwork')

!new Person('CarlosMendesIPN')
!CarlosMendesIPN.name := 'Carlos Mendes'
!CarlosMendesIPN.phone := '+351-21-998-7654'
!CarlosMendesIPN.website := 'www.carlosmendes.pt'
!CarlosMendesIPN.email := 'carlos.mendes@marketingportugal.pt'
!CarlosMendesIPN.title := 'Chief Marketing Officer'

!new Address('CarlosMendesAddressIPN')
!CarlosMendesAddressIPN.city := 'Lisbon'
!CarlosMendesAddressIPN.street := 'Rua Augusta'
!CarlosMendesAddressIPN.houseNr := '45'
!insert (CarlosMendesIPN, CarlosMendesAddressIPN) into ContactContainsAddress

!new Note('CarlosMendesNoteIPN')
!CarlosMendesNoteIPN.author := 'Carlos Mendes'
!CarlosMendesNoteIPN.time := Date('2023-02-10')
!CarlosMendesNoteIPN.type := #EMAIL
!CarlosMendesNoteIPN.comment := 'Overview of strategic marketing initiatives for Q2.'
!insert (CarlosMendesIPN, CarlosMendesNoteIPN) into ContactContainsNote

!new Company('EcoEnergySystems')
!EcoEnergySystems.name := 'Eco Energy Systems'
!EcoEnergySystems.phone := '+49-89-1234-5678'
!EcoEnergySystems.website := 'www.ecoenergysystems.de'
!EcoEnergySystems.email := 'info@ecoenergysystems.de'
!EcoEnergySystems.industry := 'Renewable Energy'

!new Address('EcoEnergySystemsAddress')
!EcoEnergySystemsAddress.city := 'Munich'
!EcoEnergySystemsAddress.street := 'Sonnenstraße'
!EcoEnergySystemsAddress.houseNr := '30'
!insert (EcoEnergySystems, EcoEnergySystemsAddress) into ContactContainsAddress

!new Note('EcoEnergySystemsNoteIPN')
!EcoEnergySystemsNoteIPN.author := 'Hans Müller'
!EcoEnergySystemsNoteIPN.time := Date('2023-05-25')
!EcoEnergySystemsNoteIPN.type := #MEETING
!EcoEnergySystemsNoteIPN.comment := 'Discussion about expanding solar energy projects in Southern Europe.'
!insert (EcoEnergySystems, EcoEnergySystemsNoteIPN) into ContactContainsNote

!new Person('PaoloConti')
!PaoloConti.name := 'Paolo Conti'
!PaoloConti.phone := '+39-06-4444-5555'
!PaoloConti.website := 'www.paoloconticonsulting.it'
!PaoloConti.email := 'paolo.conti@innovationitalia.it'
!PaoloConti.title := 'Innovation Consultant'

!new Address('PaoloContiAddress')
!PaoloContiAddress.city := 'Rome'
!PaoloContiAddress.street := 'Via Condotti'
!PaoloContiAddress.houseNr := '22'
!insert (PaoloConti, PaoloContiAddress) into ContactContainsAddress

!new Note('PaoloContiNoteIPN')
!PaoloContiNoteIPN.author := 'Paolo Conti'
!PaoloContiNoteIPN.time := Date('2023-04-18')
!PaoloContiNoteIPN.type := #CALL
!PaoloContiNoteIPN.comment := 'Insights on integrating AI into customer service.'
!insert (PaoloConti, PaoloContiNoteIPN) into ContactContainsNote

!new Person('JeanBaptiste')
!JeanBaptiste.name := 'Jean Baptiste'
!JeanBaptiste.phone := '+33-1-7543-2109'
!JeanBaptiste.website := 'www.jeanbaptiste.fr'
!JeanBaptiste.email := 'jean.baptiste@entrepreneurfrance.fr'
!JeanBaptiste.title := 'Entrepreneur'

!new Address('JeanBaptisteAddress')
!JeanBaptisteAddress.city := 'Paris'
!JeanBaptisteAddress.street := 'Champs-Élysées'
!JeanBaptisteAddress.houseNr := '12'
!insert (JeanBaptiste, JeanBaptisteAddress) into ContactContainsAddress

!new Note('JeanBaptisteNoteIPN')
!JeanBaptisteNoteIPN.author := 'Jean Baptiste'
!JeanBaptisteNoteIPN.time := Date('2023-03-30')
!JeanBaptisteNoteIPN.type := #EMAIL
!JeanBaptisteNoteIPN.comment := 'Proposal for joint ventures in sustainable agriculture.'
!insert (JeanBaptiste, JeanBaptisteNoteIPN) into ContactContainsNote

!new Relationship('CarlosToPaoloBoss')
!CarlosToPaoloBoss.type := #BOSS
!insert (CarlosToPaoloBoss, PaoloConti) into RelationshipToContact
!insert (CarlosMendesIPN, CarlosToPaoloBoss) into ContactToRelationship

!new Relationship('PaoloToCarlosEmployee')
!PaoloToCarlosEmployee.type := #EMPLOYEE
!insert (PaoloToCarlosEmployee, CarlosMendesIPN) into RelationshipToContact
!insert (PaoloConti, PaoloToCarlosEmployee) into ContactToRelationship

!new Relationship('CarlosToJeanCoworker')
!CarlosToJeanCoworker.type := #COWORKER
!insert (CarlosToJeanCoworker, JeanBaptiste) into RelationshipToContact
!insert (CarlosMendesIPN, CarlosToJeanCoworker) into ContactToRelationship

!new Relationship('JeanToCarlosCoworker')
!JeanToCarlosCoworker.type := #COWORKER
!insert (JeanToCarlosCoworker, CarlosMendesIPN) into RelationshipToContact
!insert (JeanBaptiste, JeanToCarlosCoworker) into ContactToRelationship

!new Relationship('JeanToEcoSubdivision')
!JeanToEcoSubdivision.type := #SUBDIVISION
!insert (JeanToEcoSubdivision, EcoEnergySystems) into RelationshipToContact
!insert (JeanBaptiste, JeanToEcoSubdivision) into ContactToRelationship

!insert (InternationalProfessionalNetwork, CarlosMendesIPN) into AddressBookMadeOfContact
!insert (InternationalProfessionalNetwork, EcoEnergySystems) into AddressBookMadeOfContact
!insert (InternationalProfessionalNetwork, PaoloConti) into AddressBookMadeOfContact
!insert (InternationalProfessionalNetwork, JeanBaptiste) 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: "Healthcare Professionals Address Book"

### Address Book
- **AddressBook**: "Healthcare Professionals Address Book"
  - This address book is used to manage connections and information among healthcare professionals, clinics, and pharmaceutical companies.

### Contacts
- **Contact 1**: "Wellness Pharmaceuticals"
  - **Type**: Company
  - **Attributes**:
    - Name: Wellness Pharmaceuticals
    - Phone: +1-800-987-6543
    - Website: www.wellnesspharma.com
    - Email: contact@wellnesspharma.com
    - Industry: Pharmaceuticals
  - **Addresses**:
    - Address 1:
      - City: Boston
      - HouseNr: 525
      - Street: Cambridge Street
  - **Notes**:
    - Note 1:
      - Author: Dr. Emily Chen
      - Time: "2023-08-10"
      - Type: CALL
      - Comment: Discussed the side effects of the new medication batch.

- **Contact 2**: "Dr. Emily Chen"
  - **Type**: Person
  - **Attributes**:
    - Name: Dr. Emily Chen
    - Phone: +44-20-555-0194
    - Website: 
    - Email: emily.chen@healthclinic.com
    - Title: Cardiologist
  - **Addresses**:
    - Address 1:
      - City: London
      - HouseNr: 78
      - Street: Harley Street
    - Address 2:
      - City: Manchester
      - HouseNr: 14
      - Street: Health Avenue
  - **Notes**:
    - Note 1:
      - Author: Wellness Pharmaceuticals
      - Time: "2023-09-12"
      - Type: EMAIL
      - Comment: Sent detailed report on drug interactions.

- **Contact 3**: "Sunshine Dental Clinic"
  - **Type**: Company
  - **Attributes**:
    - Name: Sunshine Dental Clinic
    - Phone: +61-2-5550-1789
    - Website: www.sunshinedental.au
    - Email: info@sunshinedental.au
    - Industry: Healthcare
  - **Addresses**:
    - Address 1:
      - City: Sydney
      - HouseNr: 34
      - Street: Oral Care Drive
    - (Boundary case: no second address)

### Relationships
- **Relationship 1**: Between "Wellness Pharmaceuticals" and "Dr. Emily Chen"
  - **Type**: BOSS
  - Target: Dr. Emily Chen

- **Relationship 2**: Between "Sunshine Dental Clinic" and "Wellness Pharmaceuticals"
  - **Type**: SUBDIVISION
  - Target: Wellness Pharmaceuticals

- **Relationship 3**: Between "Dr. Emily Chen" and "Sunshine Dental Clinic"
  - **Type**: EMPLOYEE
  - Target: Sunshine Dental Clinic

### Boundary Considerations
- Dr. Emily Chen's multiple addresses show diverse hospital affiliations, while Sunshine Dental Clinic uses fewer locations, depicting their focus on a single facility.
- Drug interaction notes emphasize the pharmacological aspect and on-call meetings for emergencies.
- Relationships illustrate hierarchical ties and professional dependencies between a clinician, a pharmaceutical company, and a dental care clinic, covering a broad spectrum of healthcare services.

<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('HealthcareProfessionalsAddressBook')

!new Company('WellnessPharmaceuticals')
!WellnessPharmaceuticals.name := 'Wellness Pharmaceuticals'
!WellnessPharmaceuticals.phone := '+1-800-987-6543'
!WellnessPharmaceuticals.website := 'www.wellnesspharma.com'
!WellnessPharmaceuticals.email := 'contact@wellnesspharma.com'
!WellnessPharmaceuticals.industry := 'Pharmaceuticals'

!new Address('WellnessPharmaAddress')
!WellnessPharmaAddress.city := 'Boston'
!WellnessPharmaAddress.houseNr := '525'
!WellnessPharmaAddress.street := 'Cambridge Street'
!insert (WellnessPharmaceuticals, WellnessPharmaAddress) into ContactContainsAddress

!new Note('WellnessPharmaNote1')
!WellnessPharmaNote1.author := 'Dr. Emily Chen'
!WellnessPharmaNote1.time := Date('2023-08-10')
!WellnessPharmaNote1.type := #CALL
!WellnessPharmaNote1.comment := 'Discussed the side effects of the new medication batch.'
!insert (WellnessPharmaceuticals, WellnessPharmaNote1) into ContactContainsNote

!new Person('DrEmilyChen')
!DrEmilyChen.name := 'Dr. Emily Chen'
!DrEmilyChen.phone := '+44-20-555-0194'
!DrEmilyChen.email := 'emily.chen@healthclinic.com'
!DrEmilyChen.title := 'Cardiologist'

!new Address('EmilyChenAddress1')
!EmilyChenAddress1.city := 'London'
!EmilyChenAddress1.houseNr := '78'
!EmilyChenAddress1.street := 'Harley Street'
!insert (DrEmilyChen, EmilyChenAddress1) into ContactContainsAddress

!new Address('EmilyChenAddress2')
!EmilyChenAddress2.city := 'Manchester'
!EmilyChenAddress2.houseNr := '14'
!EmilyChenAddress2.street := 'Health Avenue'
!insert (DrEmilyChen, EmilyChenAddress2) into ContactContainsAddress

!new Note('EmilyChenNote1')
!EmilyChenNote1.author := 'Wellness Pharmaceuticals'
!EmilyChenNote1.time := Date('2023-09-12')
!EmilyChenNote1.type := #EMAIL
!EmilyChenNote1.comment := 'Sent detailed report on drug interactions.'
!insert (DrEmilyChen, EmilyChenNote1) into ContactContainsNote

!new Company('SunshineDentalClinic')
!SunshineDentalClinic.name := 'Sunshine Dental Clinic'
!SunshineDentalClinic.phone := '+61-2-5550-1789'
!SunshineDentalClinic.website := 'www.sunshinedental.au'
!SunshineDentalClinic.email := 'info@sunshinedental.au'
!SunshineDentalClinic.industry := 'Healthcare'

!new Address('SunshineDentalAddress1')
!SunshineDentalAddress1.city := 'Sydney'
!SunshineDentalAddress1.houseNr := '34'
!SunshineDentalAddress1.street := 'Oral Care Drive'
!insert (SunshineDentalClinic, SunshineDentalAddress1) into ContactContainsAddress

!new Relationship('WellnessToEmilyBoss')
!WellnessToEmilyBoss.type := #BOSS
!insert (WellnessToEmilyBoss, DrEmilyChen) into RelationshipToContact
!insert (WellnessPharmaceuticals, WellnessToEmilyBoss) into ContactToRelationship

!new Relationship('SunshineToWellnessSubdivision')
!SunshineToWellnessSubdivision.type := #SUBDIVISION
!insert (SunshineToWellnessSubdivision, WellnessPharmaceuticals) into RelationshipToContact
!insert (SunshineDentalClinic, SunshineToWellnessSubdivision) into ContactToRelationship

!new Relationship('EmilyToSunshineEmployee')
!EmilyToSunshineEmployee.type := #EMPLOYEE
!insert (EmilyToSunshineEmployee, SunshineDentalClinic) into RelationshipToContact
!insert (DrEmilyChen, EmilyToSunshineEmployee) into ContactToRelationship

!insert (HealthcareProfessionalsAddressBook, WellnessPharmaceuticals) into AddressBookMadeOfContact
!insert (HealthcareProfessionalsAddressBook, DrEmilyChen) into AddressBookMadeOfContact
!insert (HealthcareProfessionalsAddressBook, SunshineDentalClinic) 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: "Tech Innovators Circle"

The "Tech Innovators Circle" address book serves as a comprehensive registry for professionals and companies within the technology and innovation sector, highlighting global interconnections and collaborations.

#### Contacts

1. **Contact 1 - Person**
   - **Name**: Dr. Anita Desai
   - **Phone**: +91 80 2233 4455
   - **Website**: www.anitadesai.tech
   - **Email**: adesai@techresearch.in
   - **Title**: Chief Technology Officer

   - **Addresses**:
     - **1.1 Address**:
       - **City**: Bangalore
       - **Street**: Innovation Street
       - **House Number**: 147

   - **Notes**:
     - **1.1 Note**:
       - **Author**: Dr. Anita Desai
       - **Time**: "2023-07-25"
       - **Type**: CALL
       - **Comment**: "Discussed potential AI research opportunities with international collaborators."

     - **1.2 Note**:
       - **Author**: Dr. Anita Desai
       - **Time**: "2023-08-03"
       - **Type**: MEETING
       - **Comment**: "Presented findings on quantum computing advancements at the Tech Symposium."

   - **Relationships**:
     - **1.1 Relationship** to Contact 2:
       - **Type**: COWORKER

2. **Contact 2 - Person**
   - **Name**: Miguel Santos
   - **Phone**: +55 21 5555 6677
   - **Website**: www.miguelsantos.dev
   - **Email**: miguel.s@developbr.org
   - **Title**: Lead Developer

   - **Addresses**:
     - **2.1 Address**:
       - **City**: Rio de Janeiro
       - **Street**: Tech Valley
       - **House Number**: 33

   - **Notes**:
     - **2.1 Note**:
       - **Author**: Miguel Santos
       - **Time**: "2023-08-10"
       - **Type**: EMAIL
       - **Comment**: "Followed up on collaborative development project with European partners."

   - **Relationships**:
     - **2.1 Relationship** to Contact 1:
       - **Type**: COWORKER
     - **2.2 Relationship** to Contact 4:
       - **Type**: BOSS

3. **Contact 3 - Company**
   - **Name**: FutureTech Labs
   - **Phone**: +1 415 998 7654
   - **Website**: www.futuretechlabs.com
   - **Email**: info@futuretechlabs.com
   - **Industry**: Software Development

   - **Addresses**:
     - **3.1 Address**:
       - **City**: San Francisco
       - **Street**: Tomorrow Blvd
       - **House Number**: 98F

   - **Notes**:
     - **3.1 Note**:
       - **Author**: FutureTech Labs
       - **Time**: "2023-09-01"
       - **Type**: MEETING
       - **Comment**: "Hosted workshop on pioneering digital security solutions."

   - **Relationships**:
     - **3.1 Relationship** to Contact 4:
       - **Type**: SUBDIVISION

4. **Contact 4 - Company**
   - **Name**: Innovate Global
   - **Phone**: +49 221 444 7788
   - **Website**: www.innovateglobal.com
   - **Email**: contact@innovateglobal.de
   - **Industry**: Technology Consulting

   - **Addresses**:
     - **4.1 Address**:
       - **City**: Cologne
       - **Street**: Innovation Park
       - **House Number**: 502

   - **Notes**:
     - **4.1 Note**:
       - **Author**: Innovate Global
       - **Time**: "2023-09-15"
       - **Type**: CALL
       - **Comment**: "Coordinated efforts for a major tech conference partnership."

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

### Invariant Check
- **DifferentSourceTarget**: Ensured all relationship targets are distinct from their source, maintaining consistency with structural constraints.

This instance explores the complex web of connections within the global tech industry, showcasing both corporate and individual innovation leaders across continents collaborating on forward-thinking projects and initiatives.

<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('TechInnovatorsCircle')

!new Person('DrAnitaDesai')
!DrAnitaDesai.name := 'Dr. Anita Desai'
!DrAnitaDesai.phone := '+91 80 2233 4455'
!DrAnitaDesai.website := 'www.anitadesai.tech'
!DrAnitaDesai.email := 'adesai@techresearch.in'
!DrAnitaDesai.title := 'Chief Technology Officer'

!new Address('AnitaDesaiAddress')
!AnitaDesaiAddress.city := 'Bangalore'
!AnitaDesaiAddress.street := 'Innovation Street'
!AnitaDesaiAddress.houseNr := '147'
!insert (DrAnitaDesai, AnitaDesaiAddress) into ContactContainsAddress

!new Note('AnitaDesaiNote1')
!AnitaDesaiNote1.author := 'Dr. Anita Desai'
!AnitaDesaiNote1.time := Date('2023-07-25')
!AnitaDesaiNote1.type := #CALL
!AnitaDesaiNote1.comment := 'Discussed potential AI research opportunities with international collaborators.'
!insert (DrAnitaDesai, AnitaDesaiNote1) into ContactContainsNote

!new Note('AnitaDesaiNote2')
!AnitaDesaiNote2.author := 'Dr. Anita Desai'
!AnitaDesaiNote2.time := Date('2023-08-03')
!AnitaDesaiNote2.type := #MEETING
!AnitaDesaiNote2.comment := 'Presented findings on quantum computing advancements at the Tech Symposium.'
!insert (DrAnitaDesai, AnitaDesaiNote2) into ContactContainsNote

!new Person('MiguelSantos')
!MiguelSantos.name := 'Miguel Santos'
!MiguelSantos.phone := '+55 21 5555 6677'
!MiguelSantos.website := 'www.miguelsantos.dev'
!MiguelSantos.email := 'miguel.s@developbr.org'
!MiguelSantos.title := 'Lead Developer'

!new Address('MiguelSantosAddress')
!MiguelSantosAddress.city := 'Rio de Janeiro'
!MiguelSantosAddress.street := 'Tech Valley'
!MiguelSantosAddress.houseNr := '33'
!insert (MiguelSantos, MiguelSantosAddress) into ContactContainsAddress

!new Note('MiguelSantosNote')
!MiguelSantosNote.author := 'Miguel Santos'
!MiguelSantosNote.time := Date('2023-08-10')
!MiguelSantosNote.type := #EMAIL
!MiguelSantosNote.comment := 'Followed up on collaborative development project with European partners.'
!insert (MiguelSantos, MiguelSantosNote) into ContactContainsNote

!new Company('FutureTechLabs')
!FutureTechLabs.name := 'FutureTech Labs'
!FutureTechLabs.phone := '+1 415 998 7654'
!FutureTechLabs.website := 'www.futuretechlabs.com'
!FutureTechLabs.email := 'info@futuretechlabs.com'
!FutureTechLabs.industry := 'Software Development'

!new Address('FutureTechAddress')
!FutureTechAddress.city := 'San Francisco'
!FutureTechAddress.street := 'Tomorrow Blvd'
!FutureTechAddress.houseNr := '98F'
!insert (FutureTechLabs, FutureTechAddress) into ContactContainsAddress

!new Note('FutureTechNote')
!FutureTechNote.author := 'FutureTech Labs'
!FutureTechNote.time := Date('2023-09-01')
!FutureTechNote.type := #MEETING
!FutureTechNote.comment := 'Hosted workshop on pioneering digital security solutions.'
!insert (FutureTechLabs, FutureTechNote) into ContactContainsNote

!new Company('InnovateGlobal')
!InnovateGlobal.name := 'Innovate Global'
!InnovateGlobal.phone := '+49 221 444 7788'
!InnovateGlobal.website := 'www.innovateglobal.com'
!InnovateGlobal.email := 'contact@innovateglobal.de'
!InnovateGlobal.industry := 'Technology Consulting'

!new Address('InnovateGlobalAddress')
!InnovateGlobalAddress.city := 'Cologne'
!InnovateGlobalAddress.street := 'Innovation Park'
!InnovateGlobalAddress.houseNr := '502'
!insert (InnovateGlobal, InnovateGlobalAddress) into ContactContainsAddress

!new Note('InnovateGlobalNote')
!InnovateGlobalNote.author := 'Innovate Global'
!InnovateGlobalNote.time := Date('2023-09-15')
!InnovateGlobalNote.type := #CALL
!InnovateGlobalNote.comment := 'Coordinated efforts for a major tech conference partnership.'
!insert (InnovateGlobal, InnovateGlobalNote) into ContactContainsNote

!new Relationship('AnitaToMiguelCoworker')
!AnitaToMiguelCoworker.type := #COWORKER
!insert (AnitaToMiguelCoworker, MiguelSantos) into RelationshipToContact
!insert (DrAnitaDesai, AnitaToMiguelCoworker) into ContactToRelationship

!new Relationship('MiguelToAnitaCoworker')
!MiguelToAnitaCoworker.type := #COWORKER
!insert (MiguelToAnitaCoworker, DrAnitaDesai) into RelationshipToContact
!insert (MiguelSantos, MiguelToAnitaCoworker) into ContactToRelationship

!new Relationship('MiguelToInnovateBoss')
!MiguelToInnovateBoss.type := #BOSS
!insert (MiguelToInnovateBoss, InnovateGlobal) into RelationshipToContact
!insert (MiguelSantos, MiguelToInnovateBoss) into ContactToRelationship

!new Relationship('FutureTechToInnovateSubdivision')
!FutureTechToInnovateSubdivision.type := #SUBDIVISION
!insert (FutureTechToInnovateSubdivision, InnovateGlobal) into RelationshipToContact
!insert (FutureTechLabs, FutureTechToInnovateSubdivision) into ContactToRelationship

!new Relationship('InnovateToFutureTechBoss')
!InnovateToFutureTechBoss.type := #BOSS
!insert (InnovateToFutureTechBoss, FutureTechLabs) into RelationshipToContact
!insert (InnovateGlobal, InnovateToFutureTechBoss) into ContactToRelationship

!new Relationship('InnovateToMiguelEmployee')
!InnovateToMiguelEmployee.type := #EMPLOYEE
!insert (InnovateToMiguelEmployee, MiguelSantos) into RelationshipToContact
!insert (InnovateGlobal, InnovateToMiguelEmployee) into ContactToRelationship

!insert (TechInnovatorsCircle, DrAnitaDesai) into AddressBookMadeOfContact
!insert (TechInnovatorsCircle, MiguelSantos) into AddressBookMadeOfContact
!insert (TechInnovatorsCircle, FutureTechLabs) into AddressBookMadeOfContact
!insert (TechInnovatorsCircle, InnovateGlobal) 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, an address book is used for managing a sprawling network of a global research consortium partnered with diverse non-profit organizations. The scenario presents intricate inter-organizational relationships and rich documentation through collaborative notes and addresses, emphasizing the unusual interconnectedness in non-profit and academic sectors.

### Address Book Instance
- **AddressBook: Global Research Consortium Directory**

### Contacts
1. **Contact (Company)**
   - **Name**: GreenEarth Initiative
   - **Phone**: +27-11-2345678
   - **Website**: www.greenearth.org.za
   - **Email**: contact@greenearth.org.za
   - **Industry**: Environmental Advocacy
   - **Notes**:
     - **Note 1**:
       - **Author**: Jonathan Ndlovu
       - **Time**: "2023-09-05T12:00:00"
       - **Type**: EMAIL
       - **Comment**: Submission for environmental policy reform proposal.
   - **Address**:
     - **City**: Johannesburg
     - **HouseNr**: 50
     - **Street**: Green Lane
   - **Relationships**:
     - **To**: Dr. Anika Rajan (Relation: COWORKER)
     - **To**: For Future Generations (Relation: SUBDIVISION)

2. **Contact (Company)**
   - **Name**: For Future Generations
   - **Phone**: +91-22-5556789
   - **Website**: www.futuregenerations.in
   - **Email**: info@futuregenerations.in
   - **Industry**: Education and Research
   - **Notes**:
     - **Note 1**:
       - **Author**: Sneha Kapoor
       - **Time**: "2023-07-18T14:30:00"
       - **Type**: MEETING
       - **Comment**: Regional conference on sustainable development goals.
   - **Address**:
     - **City**: Mumbai
     - **HouseNr**: 101
     - **Street**: Millennial Way
   - **Relationships**:
     - **To**: GreenEarth Initiative (Relation: BOSS)
     - **To**: Dr. Anika Rajan (Relation: BOSS)

3. **Contact (Person)**
   - **Name**: Dr. Anika Rajan
   - **Phone**: +49-30-7779955
   - **Website**: www.anikarajan.org
   - **Email**: anika.rajan@researcher.de
   - **Title**: Sustainability Scientist
   - **Notes**:
     - **Note 1**:
       - **Author**: Dr. Anika Rajan
       - **Time**: "2023-08-25T09:00:00"
       - **Type**: CALL
       - **Comment**: Discussed collaboration on climate change models.
     - **Note 2**:
       - **Author**: Dr. Anika Rajan
       - **Time**: "2023-06-10T10:15:00"
       - **Type**: EMAIL
       - **Comment**: Sent project updates and next steps overview.
   - **Address**:
     - **City**: Berlin
     - **HouseNr**: 5
     - **Street**: Innovation Allee
   - **Relationships**:
     - **To**: GreenEarth Initiative (Relation: COWORKER)
     - **To**: For Future Generations (Relation: EMPLOYEE)

4. **Contact (Company)**
   - **Name**: OceanSaver Coalition
   - **Phone**: +81-3-4567890
   - **Website**: www.oceansaver.jp
   - **Email**: admin@oceansaver.jp
   - **Industry**: Marine Conservation
   - **Notes**:
     - **Note 1**:
       - **Author**: Yukiko Tanaka
       - **Time**: "2023-05-29T15:00:00"
       - **Type**: MEETING
       - **Comment**: Broader outreach for Pacific marine life preservation.
   - **Address**:
     - **City**: Tokyo
     - **HouseNr**: 7
     - **Street**: Ocean Drive
   - **Relationships**:
     - **To**: Dr. Anika Rajan (Relation: SUBDIVISION)

### Edge Case Details
- **Non-Profit Scope**: Focuses on collaboration between non-profits and academic personalities across continents like Africa, India, Germany, and Japan, reflecting a rare corporate-academic-non-profit collaboration.
- **Multilayered Relationships**: Non-standard managerial hierarchy with shared leadership roles and mutual cooperation.
- **Diverse Expertise**: Dr. Anika Rajan functions as a central figure in both research and advocacy, connecting varied entities across educational, research, and advocacy sectors.
- **Cross-industry Collaboration**: Presents unique settings where diverse industries such as marine conservation and environmental advocacy intersect, emphasizing uncommon alliances.

<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('GlobalResearchConsortiumDirectory')

!new Company('GreenEarthInitiative')
!GreenEarthInitiative.name := 'GreenEarth Initiative'
!GreenEarthInitiative.phone := '+27-11-2345678'
!GreenEarthInitiative.website := 'www.greenearth.org.za'
!GreenEarthInitiative.email := 'contact@greenearth.org.za'
!GreenEarthInitiative.industry := 'Environmental Advocacy'

!new Address('GreenEarthAddress')
!GreenEarthAddress.city := 'Johannesburg'
!GreenEarthAddress.houseNr := '50'
!GreenEarthAddress.street := 'Green Lane'
!insert (GreenEarthInitiative, GreenEarthAddress) into ContactContainsAddress

!new Note('GreenEarthNote1')
!GreenEarthNote1.author := 'Jonathan Ndlovu'
!GreenEarthNote1.time := Date('2023-09-05T12:00:00')
!GreenEarthNote1.type := #EMAIL
!GreenEarthNote1.comment := 'Submission for environmental policy reform proposal.'
!insert (GreenEarthInitiative, GreenEarthNote1) into ContactContainsNote

!new Company('ForFutureGenerations')
!ForFutureGenerations.name := 'For Future Generations'
!ForFutureGenerations.phone := '+91-22-5556789'
!ForFutureGenerations.website := 'www.futuregenerations.in'
!ForFutureGenerations.email := 'info@futuregenerations.in'
!ForFutureGenerations.industry := 'Education and Research'

!new Address('ForFutureGenerationsAddress')
!ForFutureGenerationsAddress.city := 'Mumbai'
!ForFutureGenerationsAddress.houseNr := '101'
!ForFutureGenerationsAddress.street := 'Millennial Way'
!insert (ForFutureGenerations, ForFutureGenerationsAddress) into ContactContainsAddress

!new Note('ForFutureGenerationsNote1')
!ForFutureGenerationsNote1.author := 'Sneha Kapoor'
!ForFutureGenerationsNote1.time := Date('2023-07-18T14:30:00')
!ForFutureGenerationsNote1.type := #MEETING
!ForFutureGenerationsNote1.comment := 'Regional conference on sustainable development goals.'
!insert (ForFutureGenerations, ForFutureGenerationsNote1) into ContactContainsNote

!new Person('DrAnikaRajan')
!DrAnikaRajan.name := 'Dr. Anika Rajan'
!DrAnikaRajan.phone := '+49-30-7779955'
!DrAnikaRajan.website := 'www.anikarajan.org'
!DrAnikaRajan.email := 'anika.rajan@researcher.de'
!DrAnikaRajan.title := 'Sustainability Scientist'

!new Address('AnikaRajanAddress')
!AnikaRajanAddress.city := 'Berlin'
!AnikaRajanAddress.houseNr := '5'
!AnikaRajanAddress.street := 'Innovation Allee'
!insert (DrAnikaRajan, AnikaRajanAddress) into ContactContainsAddress

!new Note('AnikaRajanNote1')
!AnikaRajanNote1.author := 'Dr. Anika Rajan'
!AnikaRajanNote1.time := Date('2023-08-25T09:00:00')
!AnikaRajanNote1.type := #CALL
!AnikaRajanNote1.comment := 'Discussed collaboration on climate change models.'
!insert (DrAnikaRajan, AnikaRajanNote1) into ContactContainsNote

!new Note('AnikaRajanNote2')
!AnikaRajanNote2.author := 'Dr. Anika Rajan'
!AnikaRajanNote2.time := Date('2023-06-10T10:15:00')
!AnikaRajanNote2.type := #EMAIL
!AnikaRajanNote2.comment := 'Sent project updates and next steps overview.'
!insert (DrAnikaRajan, AnikaRajanNote2) into ContactContainsNote

!new Company('OceanSaverCoalition')
!OceanSaverCoalition.name := 'OceanSaver Coalition'
!OceanSaverCoalition.phone := '+81-3-4567890'
!OceanSaverCoalition.website := 'www.oceansaver.jp'
!OceanSaverCoalition.email := 'admin@oceansaver.jp'
!OceanSaverCoalition.industry := 'Marine Conservation'

!new Address('OceanSaverAddress')
!OceanSaverAddress.city := 'Tokyo'
!OceanSaverAddress.houseNr := '7'
!OceanSaverAddress.street := 'Ocean Drive'
!insert (OceanSaverCoalition, OceanSaverAddress) into ContactContainsAddress

!new Note('OceanSaverNote1')
!OceanSaverNote1.author := 'Yukiko Tanaka'
!OceanSaverNote1.time := Date('2023-05-29T15:00:00')
!OceanSaverNote1.type := #MEETING
!OceanSaverNote1.comment := 'Broader outreach for Pacific marine life preservation.'
!insert (OceanSaverCoalition, OceanSaverNote1) into ContactContainsNote

!new Relationship('GreenEarthToAnikaCoworker')
!GreenEarthToAnikaCoworker.type := #COWORKER
!insert (GreenEarthToAnikaCoworker, DrAnikaRajan) into RelationshipToContact
!insert (GreenEarthInitiative, GreenEarthToAnikaCoworker) into ContactToRelationship

!new Relationship('GreenEarthToFutureSubdivision')
!GreenEarthToFutureSubdivision.type := #SUBDIVISION
!insert (GreenEarthToFutureSubdivision, ForFutureGenerations) into RelationshipToContact
!insert (GreenEarthInitiative, GreenEarthToFutureSubdivision) into ContactToRelationship

!new Relationship('FutureToGreenEarthBoss')
!FutureToGreenEarthBoss.type := #BOSS
!insert (FutureToGreenEarthBoss, GreenEarthInitiative) into RelationshipToContact
!insert (ForFutureGenerations, FutureToGreenEarthBoss) into ContactToRelationship

!new Relationship('FutureToAnikaBoss')
!FutureToAnikaBoss.type := #BOSS
!insert (FutureToAnikaBoss, DrAnikaRajan) into RelationshipToContact
!insert (ForFutureGenerations, FutureToAnikaBoss) into ContactToRelationship

!new Relationship('AnikaToGreenEarthCoworker')
!AnikaToGreenEarthCoworker.type := #COWORKER
!insert (AnikaToGreenEarthCoworker, GreenEarthInitiative) into RelationshipToContact
!insert (DrAnikaRajan, AnikaToGreenEarthCoworker) into ContactToRelationship

!new Relationship('AnikaToFutureEmployee')
!AnikaToFutureEmployee.type := #EMPLOYEE
!insert (AnikaToFutureEmployee, ForFutureGenerations) into RelationshipToContact
!insert (DrAnikaRajan, AnikaToFutureEmployee) into ContactToRelationship

!new Relationship('OceanSaverToAnikaSubdivision')
!OceanSaverToAnikaSubdivision.type := #SUBDIVISION
!insert (OceanSaverToAnikaSubdivision, DrAnikaRajan) into RelationshipToContact
!insert (OceanSaverCoalition, OceanSaverToAnikaSubdivision) into ContactToRelationship

!insert (GlobalResearchConsortiumDirectory, GreenEarthInitiative) into AddressBookMadeOfContact
!insert (GlobalResearchConsortiumDirectory, ForFutureGenerations) into AddressBookMadeOfContact
!insert (GlobalResearchConsortiumDirectory, DrAnikaRajan) into AddressBookMadeOfContact
!insert (GlobalResearchConsortiumDirectory, OceanSaverCoalition) 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 explores a scenario within an artistic festival organization where artists and production companies collaborate on various exhibits and performances. This will highlight potential overconstraints, particularly around the flexibility of notes and the multiple relationship infrastructure typical in collaborative artistic productions.

### Instance Description

1. **AddressBook**
   - **Festival Coordination Address Book**: This address book includes all contacts involved in the Art Fusion Festival.

2. **Contacts**
   - **Company A (ArtStream Productions)**:
     - **Industry**: Event Production
     - **Phone**: +44-7501-555987
     - **Website**: www.artstreamprod.uk
     - **Email**: contact@artstreamprod.uk
     - **Addresses**:
       - **Address 1**: 
         - City: London
         - HouseNr: 450
         - Street: Piccadilly Circus
     - **Relationships**: 
       - **Artist X**: BOSS (TARGET: Artist X)
       - **Festival Coordinator**: COWORKER (TARGET: Festival Coordinator)

   - **Artist X (Elena Garcia)**:
     - **Title**: Visual Artist
     - **Phone**: +34-919-555132
     - **Email**: elena.garcia@artnet.es
     - **Addresses**:
       - **Address 1**:
         - City: Madrid
         - HouseNr: 25
         - Street: Painter's Alley
     - **Relationships**:
       - **Company A**: EMPLOYEE (TARGET: Company A)
       - **Artist Y**: COWORKER (TARGET: Artist Y)

   - **Artist Y (Roan Lee)**:
     - **Title**: Performance Artist
     - **Phone**: +82-10-5554098
     - **Email**: roan.lee@performances.kr
     - **Addresses**:
       - **Address 1**:
         - City: Seoul
         - HouseNr: 88
         - Street: Culture Street
     - **Relationships**:
       - **Artist X**: COWORKER (TARGET: Artist X)
       - **Festival Coordinator**: EMPLOYEE (TARGET: Festival Coordinator)

   - **Festival Coordinator (Mia T.)**:
     - **Industry**: Event Management
     - **Phone**: +1-202-555-0191
     - **Email**: mia.t@festivalcoord.com
     - **Addresses**:
       - **Address 1**:
         - City: New York
         - HouseNr: 1000
         - Street: Event Blvd

3. **Notes**
   - **Note for Artist X**:
     - **Author**: Elena Garcia
     - **Time**: 2023-10-05
     - **Type**: MEETING
     - **Comment**: Discuss installation logistics with ArtStream Productions.
   - **Note for Festival Coordinator**:
     - **Author**: Roan Lee
     - **Time**: 2023-09-20
     - **Type**: CALL
     - **Comment**: Finalize schedule for performance timetable.
   - **Note for ArtStream Productions**: (Exceeding intentional note inclusion)
     - **Author**: Festival Committee
     - **Time**: 2023-10-02
     - **Type**: EMAIL
     - **Comment**: Confirm stage arrangements for the opening ceremony.

### Overconstraint Analysis

- **Violation**: The model's constraint on the unique relationship nature per contact is challenged by the interconnectedness in this festival setting, where entities like Artist X and Festival Coordinator have complex networks with multiple vital relationships and roles. Additionally, the "ContactContainsNote" constraint is bypassed, revealing a need for multiple, diverse note types within single entities that the model currently limits.

- **Insight**: To accommodate such artistic festival collaborations, the model would benefit from more flexible relationship paths and permission for overlapping roles. Additionally, broadening the note association would more accurately capture real-world communication flows between artists, organizers, and production companies in creative industries. This reveals potential overconstraints that limit nuanced documentation of interactive and collaborative structures crucial in multi-participant events.

The last output is partially incorrect: 
temp.soil> !MiaT.title := 'Festival Coordinator'
temp.soil> !MiaT.industry := 'Event Management'
<input>:1:0: Class `Person' does not have an attribute `industry'.

Please provide the complete output corrected

<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('FestivalCoordinationAddressBook')

!new Company('ArtStreamProductions')
!ArtStreamProductions.name := 'ArtStream Productions'
!ArtStreamProductions.phone := '+44-7501-555987'
!ArtStreamProductions.website := 'www.artstreamprod.uk'
!ArtStreamProductions.email := 'contact@artstreamprod.uk'
!ArtStreamProductions.industry := 'Event Production'

!new Address('ArtStreamProductionsAddress')
!ArtStreamProductionsAddress.city := 'London'
!ArtStreamProductionsAddress.houseNr := '450'
!ArtStreamProductionsAddress.street := 'Piccadilly Circus'
!insert (ArtStreamProductions, ArtStreamProductionsAddress) into ContactContainsAddress

!new Note('ArtStreamProductionsNote1')
!ArtStreamProductionsNote1.author := 'Festival Committee'
!ArtStreamProductionsNote1.time := Date('2023-10-02')
!ArtStreamProductionsNote1.type := #EMAIL
!ArtStreamProductionsNote1.comment := 'Confirm stage arrangements for the opening ceremony.'
!insert (ArtStreamProductions, ArtStreamProductionsNote1) into ContactContainsNote

!new Person('ElenaGarcia')
!ElenaGarcia.name := 'Elena Garcia'
!ElenaGarcia.phone := '+34-919-555132'
!ElenaGarcia.email := 'elena.garcia@artnet.es'
!ElenaGarcia.title := 'Visual Artist'

!new Address('ElenaGarciaAddress')
!ElenaGarciaAddress.city := 'Madrid'
!ElenaGarciaAddress.houseNr := '25'
!ElenaGarciaAddress.street := 'Painter\'s Alley'
!insert (ElenaGarcia, ElenaGarciaAddress) into ContactContainsAddress

!new Note('ElenaGarciaNote1')
!ElenaGarciaNote1.author := 'Elena Garcia'
!ElenaGarciaNote1.time := Date('2023-10-05')
!ElenaGarciaNote1.type := #MEETING
!ElenaGarciaNote1.comment := 'Discuss installation logistics with ArtStream Productions.'
!insert (ElenaGarcia, ElenaGarciaNote1) into ContactContainsNote

!new Person('RoanLee')
!RoanLee.name := 'Roan Lee'
!RoanLee.phone := '+82-10-5554098'
!RoanLee.email := 'roan.lee@performances.kr'
!RoanLee.title := 'Performance Artist'

!new Address('RoanLeeAddress')
!RoanLeeAddress.city := 'Seoul'
!RoanLeeAddress.houseNr := '88'
!RoanLeeAddress.street := 'Culture Street'
!insert (RoanLee, RoanLeeAddress) into ContactContainsAddress

!new Note('RoanLeeNote1')
!RoanLeeNote1.author := 'Roan Lee'
!RoanLeeNote1.time := Date('2023-09-20')
!RoanLeeNote1.type := #CALL
!RoanLeeNote1.comment := 'Finalize schedule for performance timetable.'
!insert (RoanLee, RoanLeeNote1) into ContactContainsNote

!new Person('MiaT')
!MiaT.name := 'Mia T.'
!MiaT.phone := '+1-202-555-0191'
!MiaT.email := 'mia.t@festivalcoord.com'
!MiaT.title := 'Festival Coordinator'

!new Address('MiaTAddress')
!MiaTAddress.city := 'New York'
!MiaTAddress.houseNr := '1000'
!MiaTAddress.street := 'Event Blvd'
!insert (MiaT, MiaTAddress) into ContactContainsAddress

!new Relationship('ArtStreamToElenaBoss')
!ArtStreamToElenaBoss.type := #BOSS
!insert (ArtStreamToElenaBoss, ElenaGarcia) into RelationshipToContact
!insert (ArtStreamProductions, ArtStreamToElenaBoss) into ContactToRelationship

!new Relationship('ArtStreamToMiaCoworker')
!ArtStreamToMiaCoworker.type := #COWORKER
!insert (ArtStreamToMiaCoworker, MiaT) into RelationshipToContact
!insert (ArtStreamProductions, ArtStreamToMiaCoworker) into ContactToRelationship

!new Relationship('ElenaToArtStreamEmployee')
!ElenaToArtStreamEmployee.type := #EMPLOYEE
!insert (ElenaToArtStreamEmployee, ArtStreamProductions) into RelationshipToContact
!insert (ElenaGarcia, ElenaToArtStreamEmployee) into ContactToRelationship

!new Relationship('ElenaToRoanCoworker')
!ElenaToRoanCoworker.type := #COWORKER
!insert (ElenaToRoanCoworker, RoanLee) into RelationshipToContact
!insert (ElenaGarcia, ElenaToRoanCoworker) into ContactToRelationship

!new Relationship('RoanToElenaCoworker')
!RoanToElenaCoworker.type := #COWORKER
!insert (RoanToElenaCoworker, ElenaGarcia) into RelationshipToContact
!insert (RoanLee, RoanToElenaCoworker) into ContactToRelationship

!new Relationship('RoanToMiaEmployee')
!RoanToMiaEmployee.type := #EMPLOYEE
!insert (RoanToMiaEmployee, MiaT) into RelationshipToContact
!insert (RoanLee, RoanToMiaEmployee) into ContactToRelationship

!insert (FestivalCoordinationAddressBook, ArtStreamProductions) into AddressBookMadeOfContact
!insert (FestivalCoordinationAddressBook, ElenaGarcia) into AddressBookMadeOfContact
!insert (FestivalCoordinationAddressBook, RoanLee) into AddressBookMadeOfContact
!insert (FestivalCoordinationAddressBook, MiaT) into AddressBookMadeOfContact
</object_model>