AddressBook / gen5

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: Global Enterprise Connections

### Address Book
- **Name**: Global Enterprise Connections

### Contacts

#### 1. Person Contact
- **Name**: Nneka Okafor
- **Phone**: +234-703-555-1234
- **Website**: www.nnekaokafor.ng
- **Email**: nneka.okafor@africatechnology.ng
- **Title**: Chief Technology Officer

##### Notes for Nneka Okafor
1. **Note**
   - **Author**: Nneka Okafor
   - **Time**: "2023-05-10"
   - **Type**: CALL
   - **Comment**: Follow-up with partners on the integration of blockchain technologies.

##### Address for Nneka Okafor
- **City**: Lagos
- **House Number**: 118
- **Street**: Victoria Island

##### Relationships for Nneka Okafor
1. **Relationship**
   - **Type**: BOSS
   - **Target**: Samuel Mensah

2. **Relationship**
   - **Type**: SUBDIVISION
   - **Target**: Digital Innovations Consortium

#### 2. Company Contact
- **Name**: Digital Innovations Consortium
- **Phone**: +1-415-999-8888
- **Website**: www.digitalinnovations.com
- **Email**: info@digitalinnovations.com
- **Industry**: Technology

##### Notes for Digital Innovations Consortium
- **Note**
  - **Author**: Laura Johnson
  - **Time**: "2023-07-29"
  - **Type**: MEETING
  - **Comment**: Strategic planning session for expansion in African markets.

##### Address for Digital Innovations Consortium
1. **Address**
   - **City**: San Francisco
   - **House Number**: 200
   - **Street**: Market Street

#### 3. Person Contact
- **Name**: Samuel Mensah
- **Phone**: +233-24-888-5555
- **Website**: www.samuelmensah.edu.gh
- **Email**: samuel.mensah@ghanatech.com
- **Title**: Data Scientist

##### Notes for Samuel Mensah
- **Note**
  - **Author**: Samuel Mensah
  - **Time**: "2023-04-22"
  - **Type**: EMAIL
  - **Comment**: Preliminary report on data analytics for market trends.

##### Address for Samuel Mensah
- **City**: Accra
- **House Number**: 9
- **Street**: Kwame Nkrumah Avenue

##### Relationships for Samuel Mensah
- **Relationship**
  - **Type**: EMPLOYEE
  - **Target**: Nneka Okafor

#### 4. Person Contact
- **Name**: Laura Johnson
- **Phone**: +44-20-1234-6789
- **Website**: www.laurajohnsonconsulting.co.uk
- **Email**: laura.johnson@businessstrategy.co.uk
- **Title**: Strategic Development Manager

##### Notes for Laura Johnson
- **Note**
  - **Author**: Laura Johnson
  - **Time**: "2023-08-12"
  - **Type**: EMAIL
  - **Comment**: Update on the partnership proposal for green tech initiatives.

##### Address for Laura Johnson
- **City**: London
- **House Number**: 80
- **Street**: Piccadilly

##### Relationships for Laura Johnson
1. **Relationship**
   - **Type**: COWORKER
   - **Target**: Nneka Okafor

### Relationships

- **Nneka Okafor** is the **BOSS** of **Samuel Mensah**.
- **Samuel Mensah** is an **EMPLOYEE** of **Nneka Okafor**.
- **Nneka Okafor** is involved in **SUBDIVISION** activities with **Digital Innovations Consortium**.
- **Nneka Okafor** and **Laura Johnson** collaborate as **COWORKERS**.

This instance presents a scenario with a focus on technology and innovation, spanning continents from Africa through to Europe and the Americas. It reflects a diverse and interconnected professional network, emphasizing the lead roles and subdivisions across various geographic locations and industry domains.

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

!new Person('NnekaOkafor')
!NnekaOkafor.name := 'Nneka Okafor'
!NnekaOkafor.phone := '+234-703-555-1234'
!NnekaOkafor.website := 'www.nnekaokafor.ng'
!NnekaOkafor.email := 'nneka.okafor@africatechnology.ng'
!NnekaOkafor.title := 'Chief Technology Officer'

!new Address('NnekaOkaforAddress')
!NnekaOkaforAddress.city := 'Lagos'
!NnekaOkaforAddress.houseNr := '118'
!NnekaOkaforAddress.street := 'Victoria Island'
!insert (NnekaOkafor, NnekaOkaforAddress) into ContactContainsAddress

!new Note('NnekaOkaforNote1')
!NnekaOkaforNote1.author := 'Nneka Okafor'
!NnekaOkaforNote1.time := Date('2023-05-10')
!NnekaOkaforNote1.type := #CALL
!NnekaOkaforNote1.comment := 'Follow-up with partners on the integration of blockchain technologies.'
!insert (NnekaOkafor, NnekaOkaforNote1) into ContactContainsNote

!new Company('DigitalInnovationsConsortium')
!DigitalInnovationsConsortium.name := 'Digital Innovations Consortium'
!DigitalInnovationsConsortium.phone := '+1-415-999-8888'
!DigitalInnovationsConsortium.website := 'www.digitalinnovations.com'
!DigitalInnovationsConsortium.email := 'info@digitalinnovations.com'
!DigitalInnovationsConsortium.industry := 'Technology'

!new Address('DigitalInnovationsAddress')
!DigitalInnovationsAddress.city := 'San Francisco'
!DigitalInnovationsAddress.houseNr := '200'
!DigitalInnovationsAddress.street := 'Market Street'
!insert (DigitalInnovationsConsortium, DigitalInnovationsAddress) into ContactContainsAddress

!new Note('DigitalInnovationsNote1')
!DigitalInnovationsNote1.author := 'Laura Johnson'
!DigitalInnovationsNote1.time := Date('2023-07-29')
!DigitalInnovationsNote1.type := #MEETING
!DigitalInnovationsNote1.comment := 'Strategic planning session for expansion in African markets.'
!insert (DigitalInnovationsConsortium, DigitalInnovationsNote1) into ContactContainsNote

!new Person('SamuelMensah')
!SamuelMensah.name := 'Samuel Mensah'
!SamuelMensah.phone := '+233-24-888-5555'
!SamuelMensah.website := 'www.samuelmensah.edu.gh'
!SamuelMensah.email := 'samuel.mensah@ghanatech.com'
!SamuelMensah.title := 'Data Scientist'

!new Address('SamuelMensahAddress')
!SamuelMensahAddress.city := 'Accra'
!SamuelMensahAddress.houseNr := '9'
!SamuelMensahAddress.street := 'Kwame Nkrumah Avenue'
!insert (SamuelMensah, SamuelMensahAddress) into ContactContainsAddress

!new Note('SamuelMensahNote1')
!SamuelMensahNote1.author := 'Samuel Mensah'
!SamuelMensahNote1.time := Date('2023-04-22')
!SamuelMensahNote1.type := #EMAIL
!SamuelMensahNote1.comment := 'Preliminary report on data analytics for market trends.'
!insert (SamuelMensah, SamuelMensahNote1) into ContactContainsNote

!new Person('LauraJohnson')
!LauraJohnson.name := 'Laura Johnson'
!LauraJohnson.phone := '+44-20-1234-6789'
!LauraJohnson.website := 'www.laurajohnsonconsulting.co.uk'
!LauraJohnson.email := 'laura.johnson@businessstrategy.co.uk'
!LauraJohnson.title := 'Strategic Development Manager'

!new Address('LauraJohnsonAddress')
!LauraJohnsonAddress.city := 'London'
!LauraJohnsonAddress.houseNr := '80'
!LauraJohnsonAddress.street := 'Piccadilly'
!insert (LauraJohnson, LauraJohnsonAddress) into ContactContainsAddress

!new Note('LauraJohnsonNote1')
!LauraJohnsonNote1.author := 'Laura Johnson'
!LauraJohnsonNote1.time := Date('2023-08-12')
!LauraJohnsonNote1.type := #EMAIL
!LauraJohnsonNote1.comment := 'Update on the partnership proposal for green tech initiatives.'
!insert (LauraJohnson, LauraJohnsonNote1) into ContactContainsNote

!new Relationship('NnekaToSamuelBoss')
!NnekaToSamuelBoss.type := #BOSS
!insert (NnekaToSamuelBoss, SamuelMensah) into RelationshipToContact
!insert (NnekaOkafor, NnekaToSamuelBoss) into ContactToRelationship

!new Relationship('SamuelToNnekaEmployee')
!SamuelToNnekaEmployee.type := #EMPLOYEE
!insert (SamuelToNnekaEmployee, NnekaOkafor) into RelationshipToContact
!insert (SamuelMensah, SamuelToNnekaEmployee) into ContactToRelationship

!new Relationship('NnekaToDigitalInnovationsSubdivision')
!NnekaToDigitalInnovationsSubdivision.type := #SUBDIVISION
!insert (NnekaToDigitalInnovationsSubdivision, DigitalInnovationsConsortium) into RelationshipToContact
!insert (NnekaOkafor, NnekaToDigitalInnovationsSubdivision) into ContactToRelationship

!new Relationship('NnekaToLauraCoworker')
!NnekaToLauraCoworker.type := #COWORKER
!insert (NnekaToLauraCoworker, LauraJohnson) into RelationshipToContact
!insert (NnekaOkafor, NnekaToLauraCoworker) into ContactToRelationship

!insert (GlobalEnterpriseConnections, NnekaOkafor) into AddressBookMadeOfContact
!insert (GlobalEnterpriseConnections, DigitalInnovationsConsortium) into AddressBookMadeOfContact
!insert (GlobalEnterpriseConnections, SamuelMensah) into AddressBookMadeOfContact
!insert (GlobalEnterpriseConnections, LauraJohnson) 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: "Global Research Collaboration Address Book"

### Address Book
- **AddressBook**: "Global Research Collaboration Address Book"
  - This address book is intended to manage and facilitate collaboration among international research institutions and leading scientists in various disciplines.

### Contacts
- **Contact 1**: "International Space Research Agency"
  - **Type**: Company
  - **Attributes**:
    - Name: International Space Research Agency
    - Phone: +1-713-555-0190
    - Website: www.spaceresearch.org
    - Email: info@spaceresearch.org
    - Industry: Aerospace & Research
  - **Addresses**:
    - Address 1:
      - City: Houston
      - HouseNr: 400
      - Street: Galileo Parkway

- **Contact 2**: "Prof. Aiko Tanaka"
  - **Type**: Person
  - **Attributes**:
    - Name: Prof. Aiko Tanaka
    - Phone: +81-3-5550-7432
    - Website: www.aikotanaka.jp
    - Email: aiko.tanaka@tokyouniversity.ac.jp
    - Title: Astrophysicist
  - **Addresses**:
    - Address 1:
      - City: Tokyo
      - HouseNr: 55
      - Street: University Drive
  - **Notes**:
    - Note 1:
      - Author: International Space Research Agency
      - Time: "2023-11-15"
      - Type: MEETING
      - Comment: Held a virtual seminar on recent advancements in satellite technology.

- **Contact 3**: "Advanced Biology Institute"
  - **Type**: Company
  - **Attributes**:
    - Name: Advanced Biology Institute
    - Phone: +49-89-555-0886
    - Website: www.advancedbiologi.de
    - Email: contact@advancedbiologi.de
    - Industry: Biotechnology
  - **Addresses**:
    - (Boundary consideration with no addresses)

- **Contact 4**: "Dr. Carlos Mendes"
  - **Type**: Person
  - **Attributes**:
    - Name: Dr. Carlos Mendes
    - Phone: +55-21-555-6712
    - Website: 
    - Email: carlos.mendes@pesquisador.br
    - Title: Marine Ecologist
  - **Addresses**:
    - Address 1:
      - City: Rio de Janeiro
      - HouseNr: 101
      - Street: Ocean Street
    - Address 2:
      - City: São Paulo
      - HouseNr: 202
      - Street: Ecosystem Lane

### Relationships
- **Relationship 1**: Between "International Space Research Agency" and "Prof. Aiko Tanaka"
  - **Type**: COWORKER
  - Target: Prof. Aiko Tanaka

- **Relationship 2**: Between "Advanced Biology Institute" and "Dr. Carlos Mendes"
  - **Type**: EMPLOYEE
  - Target: Dr. Carlos Mendes

- **Relationship 3**: Between "Dr. Carlos Mendes" and "Prof. Aiko Tanaka"
  - **Type**: SUBDIVISION
  - Target: Prof. Aiko Tanaka

### Boundary Considerations
- "Advanced Biology Institute" lacks a physical address to illustrate a predominantly virtual or distributed research model.
- Professors and doctors from varied disciplines and regions, such as astrophysics and marine ecology, are included, highlighting interdisciplinary collaboration.
- Multiple addresses for Dr. Carlos Mendes display a scenario of cross-regional research involvement, emphasizing teamwork across different geographic locations.

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

!new Company('InternationalSpaceResearchAgency')
!InternationalSpaceResearchAgency.name := 'International Space Research Agency'
!InternationalSpaceResearchAgency.phone := '+1-713-555-0190'
!InternationalSpaceResearchAgency.website := 'www.spaceresearch.org'
!InternationalSpaceResearchAgency.email := 'info@spaceresearch.org'
!InternationalSpaceResearchAgency.industry := 'Aerospace & Research'

!new Address('SpaceResearchAddress')
!SpaceResearchAddress.city := 'Houston'
!SpaceResearchAddress.houseNr := '400'
!SpaceResearchAddress.street := 'Galileo Parkway'
!insert (InternationalSpaceResearchAgency, SpaceResearchAddress) into ContactContainsAddress

!new Person('ProfAikoTanaka')
!ProfAikoTanaka.name := 'Prof. Aiko Tanaka'
!ProfAikoTanaka.phone := '+81-3-5550-7432'
!ProfAikoTanaka.website := 'www.aikotanaka.jp'
!ProfAikoTanaka.email := 'aiko.tanaka@tokyouniversity.ac.jp'
!ProfAikoTanaka.title := 'Astrophysicist'

!new Address('AikoTanakaAddress')
!AikoTanakaAddress.city := 'Tokyo'
!AikoTanakaAddress.houseNr := '55'
!AikoTanakaAddress.street := 'University Drive'
!insert (ProfAikoTanaka, AikoTanakaAddress) into ContactContainsAddress

!new Note('AikoTanakaNote1')
!AikoTanakaNote1.author := 'International Space Research Agency'
!AikoTanakaNote1.time := Date('2023-11-15')
!AikoTanakaNote1.type := #MEETING
!AikoTanakaNote1.comment := 'Held a virtual seminar on recent advancements in satellite technology.'
!insert (ProfAikoTanaka, AikoTanakaNote1) into ContactContainsNote

!new Company('AdvancedBiologyInstitute')
!AdvancedBiologyInstitute.name := 'Advanced Biology Institute'
!AdvancedBiologyInstitute.phone := '+49-89-555-0886'
!AdvancedBiologyInstitute.website := 'www.advancedbiologi.de'
!AdvancedBiologyInstitute.email := 'contact@advancedbiologi.de'
!AdvancedBiologyInstitute.industry := 'Biotechnology'

!new Person('DrCarlosMendes')
!DrCarlosMendes.name := 'Dr. Carlos Mendes'
!DrCarlosMendes.phone := '+55-21-555-6712'
!DrCarlosMendes.email := 'carlos.mendes@pesquisador.br'
!DrCarlosMendes.title := 'Marine Ecologist'

!new Address('CarlosMendesAddress1')
!CarlosMendesAddress1.city := 'Rio de Janeiro'
!CarlosMendesAddress1.houseNr := '101'
!CarlosMendesAddress1.street := 'Ocean Street'
!insert (DrCarlosMendes, CarlosMendesAddress1) into ContactContainsAddress

!new Address('CarlosMendesAddress2')
!CarlosMendesAddress2.city := 'São Paulo'
!CarlosMendesAddress2.houseNr := '202'
!CarlosMendesAddress2.street := 'Ecosystem Lane'
!insert (DrCarlosMendes, CarlosMendesAddress2) into ContactContainsAddress

!new Relationship('SpaceToAikoCoworker')
!SpaceToAikoCoworker.type := #COWORKER
!insert (SpaceToAikoCoworker, ProfAikoTanaka) into RelationshipToContact
!insert (InternationalSpaceResearchAgency, SpaceToAikoCoworker) into ContactToRelationship

!new Relationship('BiologyToCarlosEmployee')
!BiologyToCarlosEmployee.type := #EMPLOYEE
!insert (BiologyToCarlosEmployee, DrCarlosMendes) into RelationshipToContact
!insert (AdvancedBiologyInstitute, BiologyToCarlosEmployee) into ContactToRelationship

!new Relationship('CarlosToAikoSubdivision')
!CarlosToAikoSubdivision.type := #SUBDIVISION
!insert (CarlosToAikoSubdivision, ProfAikoTanaka) into RelationshipToContact
!insert (DrCarlosMendes, CarlosToAikoSubdivision) into ContactToRelationship

!insert (GlobalResearchCollaborationAddressBook, InternationalSpaceResearchAgency) into AddressBookMadeOfContact
!insert (GlobalResearchCollaborationAddressBook, ProfAikoTanaka) into AddressBookMadeOfContact
!insert (GlobalResearchCollaborationAddressBook, AdvancedBiologyInstitute) into AddressBookMadeOfContact
!insert (GlobalResearchCollaborationAddressBook, DrCarlosMendes) 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: "Healthcare Network"

The "Healthcare Network" address book acts as a comprehensive registry for professionals and institutions within the healthcare industry, capturing the network of collaborations and communications necessary in this field.

#### Contacts

1. **Contact 1 - Person**
   - **Name**: Dr. Lisa Chen
   - **Phone**: +65 6221 1122
   - **Website**: www.drlisachenmedical.com
   - **Email**: lisa.chen@wellhealth.sg
   - **Title**: Oncology Specialist

   - **Addresses**:
     - **1.1 Address**:
       - **City**: Singapore
       - **Street**: Health Avenue
       - **House Number**: 88

   - **Notes**:
     - **1.1 Note**:
       - **Author**: Dr. Lisa Chen
       - **Time**: "2023-07-05"
       - **Type**: MEETING
       - **Comment**: "Discussed new treatment protocols in regional cancer summit."

     - **1.2 Note**:
       - **Author**: Dr. Lisa Chen
       - **Time**: "2023-07-12"
       - **Type**: CALL
       - **Comment**: "Phone consultation with European experts on rare cancer cases."

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

2. **Contact 2 - Person**
   - **Name**: Prof. Mahmoud El-Nahas
   - **Phone**: +20 2 3546 8799
   - **Website**: www.mahmoudelnresearch.com
   - **Email**: mahmoud.el@medresearch.edu.eg
   - **Title**: Medical Research Director

   - **Addresses**:
     - **2.1 Address**:
       - **City**: Cairo
       - **Street**: University Road
       - **House Number**: 5

   - **Notes**:
     - **2.1 Note**:
       - **Author**: Prof. Mahmoud El-Nahas
       - **Time**: "2023-08-20"
       - **Type**: EMAIL
       - **Comment**: "Shared latest findings on genetic disorders with the global research community."

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

3. **Contact 3 - Company**
   - **Name**: MedLife Pharmaceuticals
   - **Phone**: +1 312 555 6789
   - **Website**: www.medlifepharma.com
   - **Email**: contactus@medlife.com
   - **Industry**: Pharmaceutical

   - **Addresses**:
     - **3.1 Address**:
       - **City**: Chicago
       - **Street**: Medicine Drive
       - **House Number**: 100A

   - **Notes**:
     - **3.1 Note**:
       - **Author**: MedLife Pharmaceuticals
       - **Time**: "2023-08-01"
       - **Type**: MEETING
       - **Comment**: "Annual review of research partnerships with international hospitals."

   - **Relationships**:
     - **3.1 Relationship** to Contact 1:
       - **Type**: BOSS
     - **3.2 Relationship** to Contact 4:
       - **Type**: SUBDIVISION

4. **Contact 4 - Company**
   - **Name**: Global Health Partners
   - **Phone**: +61 2 8765 4321
   - **Website**: www.globalhealthpartners.org
   - **Email**: admin@globalhealth.org
   - **Industry**: Healthcare Consulting

   - **Addresses**:
     - **4.1 Address**:
       - **City**: Sydney
       - **Street**: Healthcare Boulevard
       - **House Number**: 222

   - **Notes**:
     - **4.1 Note**:
       - **Author**: Global Health Partners
       - **Time**: "2023-08-15"
       - **Type**: EMAIL
       - **Comment**: "Coordinated a global conference on emergent health technologies."

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

### Invariant Check
- **DifferentSourceTarget**: Verified that all relationship targets are distinct from their sources, ensuring no improper self-references.

This instance delves into the collaborative fabric of the healthcare sector, illustrating the active involvement of individual professionals and companies from various global centers dedicated to advancing health sciences and treatment outcomes.

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

!new Person('DrLisaChen')
!DrLisaChen.name := 'Dr. Lisa Chen'
!DrLisaChen.phone := '+65 6221 1122'
!DrLisaChen.website := 'www.drlisachenmedical.com'
!DrLisaChen.email := 'lisa.chen@wellhealth.sg'
!DrLisaChen.title := 'Oncology Specialist'

!new Address('LisaChenAddress')
!LisaChenAddress.city := 'Singapore'
!LisaChenAddress.street := 'Health Avenue'
!LisaChenAddress.houseNr := '88'
!insert (DrLisaChen, LisaChenAddress) into ContactContainsAddress

!new Note('LisaChenNote1')
!LisaChenNote1.author := 'Dr. Lisa Chen'
!LisaChenNote1.time := Date('2023-07-05')
!LisaChenNote1.type := #MEETING
!LisaChenNote1.comment := 'Discussed new treatment protocols in regional cancer summit.'
!insert (DrLisaChen, LisaChenNote1) into ContactContainsNote

!new Note('LisaChenNote2')
!LisaChenNote2.author := 'Dr. Lisa Chen'
!LisaChenNote2.time := Date('2023-07-12')
!LisaChenNote2.type := #CALL
!LisaChenNote2.comment := 'Phone consultation with European experts on rare cancer cases.'
!insert (DrLisaChen, LisaChenNote2) into ContactContainsNote

!new Person('ProfMahmoudElNahas')
!ProfMahmoudElNahas.name := 'Prof. Mahmoud El-Nahas'
!ProfMahmoudElNahas.phone := '+20 2 3546 8799'
!ProfMahmoudElNahas.website := 'www.mahmoudelnresearch.com'
!ProfMahmoudElNahas.email := 'mahmoud.el@medresearch.edu.eg'
!ProfMahmoudElNahas.title := 'Medical Research Director'

!new Address('MahmoudElNahasAddress')
!MahmoudElNahasAddress.city := 'Cairo'
!MahmoudElNahasAddress.street := 'University Road'
!MahmoudElNahasAddress.houseNr := '5'
!insert (ProfMahmoudElNahas, MahmoudElNahasAddress) into ContactContainsAddress

!new Note('MahmoudElNahasNote')
!MahmoudElNahasNote.author := 'Prof. Mahmoud El-Nahas'
!MahmoudElNahasNote.time := Date('2023-08-20')
!MahmoudElNahasNote.type := #EMAIL
!MahmoudElNahasNote.comment := 'Shared latest findings on genetic disorders with the global research community.'
!insert (ProfMahmoudElNahas, MahmoudElNahasNote) into ContactContainsNote

!new Company('MedLifePharmaceuticals')
!MedLifePharmaceuticals.name := 'MedLife Pharmaceuticals'
!MedLifePharmaceuticals.phone := '+1 312 555 6789'
!MedLifePharmaceuticals.website := 'www.medlifepharma.com'
!MedLifePharmaceuticals.email := 'contactus@medlife.com'
!MedLifePharmaceuticals.industry := 'Pharmaceutical'

!new Address('MedLifeAddress')
!MedLifeAddress.city := 'Chicago'
!MedLifeAddress.street := 'Medicine Drive'
!MedLifeAddress.houseNr := '100A'
!insert (MedLifePharmaceuticals, MedLifeAddress) into ContactContainsAddress

!new Note('MedLifeNote')
!MedLifeNote.author := 'MedLife Pharmaceuticals'
!MedLifeNote.time := Date('2023-08-01')
!MedLifeNote.type := #MEETING
!MedLifeNote.comment := 'Annual review of research partnerships with international hospitals.'
!insert (MedLifePharmaceuticals, MedLifeNote) into ContactContainsNote

!new Company('GlobalHealthPartners')
!GlobalHealthPartners.name := 'Global Health Partners'
!GlobalHealthPartners.phone := '+61 2 8765 4321'
!GlobalHealthPartners.website := 'www.globalhealthpartners.org'
!GlobalHealthPartners.email := 'admin@globalhealth.org'
!GlobalHealthPartners.industry := 'Healthcare Consulting'

!new Address('GlobalHealthAddress')
!GlobalHealthAddress.city := 'Sydney'
!GlobalHealthAddress.street := 'Healthcare Boulevard'
!GlobalHealthAddress.houseNr := '222'
!insert (GlobalHealthPartners, GlobalHealthAddress) into ContactContainsAddress

!new Note('GlobalHealthNote')
!GlobalHealthNote.author := 'Global Health Partners'
!GlobalHealthNote.time := Date('2023-08-15')
!GlobalHealthNote.type := #EMAIL
!GlobalHealthNote.comment := 'Coordinated a global conference on emergent health technologies.'
!insert (GlobalHealthPartners, GlobalHealthNote) into ContactContainsNote

!new Relationship('LisaToMedLifeCoworker')
!LisaToMedLifeCoworker.type := #COWORKER
!insert (LisaToMedLifeCoworker, MedLifePharmaceuticals) into RelationshipToContact
!insert (DrLisaChen, LisaToMedLifeCoworker) into ContactToRelationship

!new Relationship('MahmoudToHealthPartnersEmployee')
!MahmoudToHealthPartnersEmployee.type := #EMPLOYEE
!insert (MahmoudToHealthPartnersEmployee, GlobalHealthPartners) into RelationshipToContact
!insert (ProfMahmoudElNahas, MahmoudToHealthPartnersEmployee) into ContactToRelationship

!new Relationship('MedLifeToLisaBoss')
!MedLifeToLisaBoss.type := #BOSS
!insert (MedLifeToLisaBoss, DrLisaChen) into RelationshipToContact
!insert (MedLifePharmaceuticals, MedLifeToLisaBoss) into ContactToRelationship

!new Relationship('MedLifeToGlobalHealthSubdivision')
!MedLifeToGlobalHealthSubdivision.type := #SUBDIVISION
!insert (MedLifeToGlobalHealthSubdivision, GlobalHealthPartners) into RelationshipToContact
!insert (MedLifePharmaceuticals, MedLifeToGlobalHealthSubdivision) into ContactToRelationship

!new Relationship('HealthPartnersToMahmoudBoss')
!HealthPartnersToMahmoudBoss.type := #BOSS
!insert (HealthPartnersToMahmoudBoss, ProfMahmoudElNahas) into RelationshipToContact
!insert (GlobalHealthPartners, HealthPartnersToMahmoudBoss) into ContactToRelationship

!new Relationship('HealthPartnersToMedLifeSubdivision')
!HealthPartnersToMedLifeSubdivision.type := #SUBDIVISION
!insert (HealthPartnersToMedLifeSubdivision, MedLifePharmaceuticals) into RelationshipToContact
!insert (GlobalHealthPartners, HealthPartnersToMedLifeSubdivision) into ContactToRelationship

!insert (HealthcareNetwork, DrLisaChen) into AddressBookMadeOfContact
!insert (HealthcareNetwork, ProfMahmoudElNahas) into AddressBookMadeOfContact
!insert (HealthcareNetwork, MedLifePharmaceuticals) into AddressBookMadeOfContact
!insert (HealthcareNetwork, GlobalHealthPartners) 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: 
For this edge case instance, the address book is dedicated to a multi-faceted artistic collective that spans several cultures and art forms, including artists, curators, and collaborative institutions. This scenario explores complex networks within creative industries with diverse artistic and regional nuances.

### Address Book Instance
- **AddressBook: Artistic Collective Network**

### Contacts
1. **Contact (Company)**
   - **Name**: Global Art Movement
   - **Phone**: +33-1-23456789
   - **Website**: www.globalartmovement.fr
   - **Email**: connect@globalartmovement.fr
   - **Industry**: Art and Culture
   - **Notes**:
     - **Note 1**:
       - **Author**: Amélie Dubois
       - **Time**: "2023-04-15T11:00:00"
       - **Type**: MEETING
       - **Comment**: Paris symposium on cross-cultural artistic exchange.
   - **Address**:
     - **City**: Paris
     - **HouseNr**: 220
     - **Street**: Rue de l'Artiste
   - **Relationships**:
     - **To**: Santiago Reyes (Relation: SUBDIVISION)
     - **To**: Art Haven Academy (Relation: COWORKER)

2. **Contact (Company)**
   - **Name**: Art Haven Academy
   - **Phone**: +61-3-87654321
   - **Website**: www.arthaven.edu.au
   - **Email**: admissions@arthaven.edu.au
   - **Industry**: Education and Culture
   - **Notes**:
     - **Note 1**:
       - **Author**: Oliver Nguyen
       - **Time**: "2023-03-22T14:20:00"
       - **Type**: EMAIL
       - **Comment**: Webinar on 'The Future of Art Education.'
   - **Address**:
     - **City**: Melbourne
     - **HouseNr**: 88
     - **Street**: Artistic Avenue
   - **Relationships**:
     - **To**: Global Art Movement (Relation: COWORKER)
     - **To**: Santiago Reyes (Relation: EMPLOYEE)

3. **Contact (Person)**
   - **Name**: Santiago Reyes
   - **Phone**: +34-91-6543210
   - **Website**: www.santiagoreyes.com
   - **Email**: s.reyes@artistry.com
   - **Title**: Curator
   - **Notes**:
     - **Note 1**:
       - **Author**: Santiago Reyes
       - **Time**: "2023-11-02T16:00:00"
       - **Type**: CALL
       - **Comment**: Discussion on an upcoming exhibition in Tokyo.
     - **Note 2**:
       - **Author**: Santiago Reyes
       - **Time**: "2023-07-10T10:30:00"
       - **Type**: MEETING
       - **Comment**: Artist collaboration workshop in Madrid.
   - **Address**:
     - **City**: Madrid
     - **HouseNr**: 15
     - **Street**: Paseo del Arte
   - **Relationships**:
     - **To**: Global Art Movement (Relation: SUBDIVISION)
     - **To**: Art Haven Academy (Relation: EMPLOYEE)

4. **Contact (Person)**
   - **Name**: Fiona Chen
   - **Phone**: +86-21-9876543
   - **Website**: www.fionachenstudio.cn
   - **Email**: fiona.chen@art.cn
   - **Title**: Visual Artist
   - **Notes**:
     - **Note 1**:
       - **Author**: Fiona Chen
       - **Time**: "2023-05-12T08:45:00"
       - **Type**: EMAIL
       - **Comment**: Submitted portfolio for Global Art Residency.
   - **Address**:
     - **City**: Shanghai
     - **HouseNr**: 202
     - **Street**: Culture Street
   - **Relationships**:
     - **To**: Santiago Reyes (Relation: COWORKER)

### Edge Case Details
- **Cultural Diversity**: The contacts represent collaboration across continents, from Europe to Asia to Australia, emphasizing cultural diversity and artistic integration.
- **Cross-Disciplinary Interactions**: The instance captures interactions between educational, artistic, and curation sectors, reflecting a unique blend of educational and creative roles.
- **Complex Network of Relationships**: Santiago Reyes serves as a central connecting figure bridging formal educational bodies and informal artistic collectives with multiple subordinate and coworker roles.
- **Uncommon Institutional Roles**: The setup involves institutions usually not associated with direct artistic production, like the Art Haven Academy, showing unusual educational collaborations within arts.

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

!new Company('GlobalArtMovement')
!GlobalArtMovement.name := 'Global Art Movement'
!GlobalArtMovement.phone := '+33-1-23456789'
!GlobalArtMovement.website := 'www.globalartmovement.fr'
!GlobalArtMovement.email := 'connect@globalartmovement.fr'
!GlobalArtMovement.industry := 'Art and Culture'

!new Address('GlobalArtMovementAddress')
!GlobalArtMovementAddress.city := 'Paris'
!GlobalArtMovementAddress.houseNr := '220'
!GlobalArtMovementAddress.street := 'Rue de l\'Artiste'
!insert (GlobalArtMovement, GlobalArtMovementAddress) into ContactContainsAddress

!new Note('GlobalArtMovementNote1')
!GlobalArtMovementNote1.author := 'Amélie Dubois'
!GlobalArtMovementNote1.time := Date('2023-04-15T11:00:00')
!GlobalArtMovementNote1.type := #MEETING
!GlobalArtMovementNote1.comment := 'Paris symposium on cross-cultural artistic exchange.'
!insert (GlobalArtMovement, GlobalArtMovementNote1) into ContactContainsNote

!new Company('ArtHavenAcademy')
!ArtHavenAcademy.name := 'Art Haven Academy'
!ArtHavenAcademy.phone := '+61-3-87654321'
!ArtHavenAcademy.website := 'www.arthaven.edu.au'
!ArtHavenAcademy.email := 'admissions@arthaven.edu.au'
!ArtHavenAcademy.industry := 'Education and Culture'

!new Address('ArtHavenAcademyAddress')
!ArtHavenAcademyAddress.city := 'Melbourne'
!ArtHavenAcademyAddress.houseNr := '88'
!ArtHavenAcademyAddress.street := 'Artistic Avenue'
!insert (ArtHavenAcademy, ArtHavenAcademyAddress) into ContactContainsAddress

!new Note('ArtHavenNote1')
!ArtHavenNote1.author := 'Oliver Nguyen'
!ArtHavenNote1.time := Date('2023-03-22T14:20:00')
!ArtHavenNote1.type := #EMAIL
!ArtHavenNote1.comment := 'Webinar on "The Future of Art Education."'
!insert (ArtHavenAcademy, ArtHavenNote1) into ContactContainsNote

!new Person('SantiagoReyes')
!SantiagoReyes.name := 'Santiago Reyes'
!SantiagoReyes.phone := '+34-91-6543210'
!SantiagoReyes.website := 'www.santiagoreyes.com'
!SantiagoReyes.email := 's.reyes@artistry.com'
!SantiagoReyes.title := 'Curator'

!new Address('SantiagoReyesAddress')
!SantiagoReyesAddress.city := 'Madrid'
!SantiagoReyesAddress.houseNr := '15'
!SantiagoReyesAddress.street := 'Paseo del Arte'
!insert (SantiagoReyes, SantiagoReyesAddress) into ContactContainsAddress

!new Note('SantiagoReyesNote1')
!SantiagoReyesNote1.author := 'Santiago Reyes'
!SantiagoReyesNote1.time := Date('2023-11-02T16:00:00')
!SantiagoReyesNote1.type := #CALL
!SantiagoReyesNote1.comment := 'Discussion on an upcoming exhibition in Tokyo.'
!insert (SantiagoReyes, SantiagoReyesNote1) into ContactContainsNote

!new Note('SantiagoReyesNote2')
!SantiagoReyesNote2.author := 'Santiago Reyes'
!SantiagoReyesNote2.time := Date('2023-07-10T10:30:00')
!SantiagoReyesNote2.type := #MEETING
!SantiagoReyesNote2.comment := 'Artist collaboration workshop in Madrid.'
!insert (SantiagoReyes, SantiagoReyesNote2) into ContactContainsNote

!new Person('FionaChen')
!FionaChen.name := 'Fiona Chen'
!FionaChen.phone := '+86-21-9876543'
!FionaChen.website := 'www.fionachenstudio.cn'
!FionaChen.email := 'fiona.chen@art.cn'
!FionaChen.title := 'Visual Artist'

!new Address('FionaChenAddress')
!FionaChenAddress.city := 'Shanghai'
!FionaChenAddress.houseNr := '202'
!FionaChenAddress.street := 'Culture Street'
!insert (FionaChen, FionaChenAddress) into ContactContainsAddress

!new Note('FionaChenNote1')
!FionaChenNote1.author := 'Fiona Chen'
!FionaChenNote1.time := Date('2023-05-12T08:45:00')
!FionaChenNote1.type := #EMAIL
!FionaChenNote1.comment := 'Submitted portfolio for Global Art Residency.'
!insert (FionaChen, FionaChenNote1) into ContactContainsNote

!new Relationship('GlobalArtToSantiagoSubdivision')
!GlobalArtToSantiagoSubdivision.type := #SUBDIVISION
!insert (GlobalArtToSantiagoSubdivision, SantiagoReyes) into RelationshipToContact
!insert (GlobalArtMovement, GlobalArtToSantiagoSubdivision) into ContactToRelationship

!new Relationship('GlobalArtToArtHavenCoworker')
!GlobalArtToArtHavenCoworker.type := #COWORKER
!insert (GlobalArtToArtHavenCoworker, ArtHavenAcademy) into RelationshipToContact
!insert (GlobalArtMovement, GlobalArtToArtHavenCoworker) into ContactToRelationship

!new Relationship('ArtHavenToGlobalArtCoworker')
!ArtHavenToGlobalArtCoworker.type := #COWORKER
!insert (ArtHavenToGlobalArtCoworker, GlobalArtMovement) into RelationshipToContact
!insert (ArtHavenAcademy, ArtHavenToGlobalArtCoworker) into ContactToRelationship

!new Relationship('ArtHavenToSantiagoEmployee')
!ArtHavenToSantiagoEmployee.type := #EMPLOYEE
!insert (ArtHavenToSantiagoEmployee, SantiagoReyes) into RelationshipToContact
!insert (ArtHavenAcademy, ArtHavenToSantiagoEmployee) into ContactToRelationship

!new Relationship('SantiagoToGlobalArtSubdivision')
!SantiagoToGlobalArtSubdivision.type := #SUBDIVISION
!insert (SantiagoToGlobalArtSubdivision, GlobalArtMovement) into RelationshipToContact
!insert (SantiagoReyes, SantiagoToGlobalArtSubdivision) into ContactToRelationship

!new Relationship('SantiagoToArtHavenEmployee')
!SantiagoToArtHavenEmployee.type := #EMPLOYEE
!insert (SantiagoToArtHavenEmployee, ArtHavenAcademy) into RelationshipToContact
!insert (SantiagoReyes, SantiagoToArtHavenEmployee) into ContactToRelationship

!new Relationship('FionaToSantiagoCoworker')
!FionaToSantiagoCoworker.type := #COWORKER
!insert (FionaToSantiagoCoworker, SantiagoReyes) into RelationshipToContact
!insert (FionaChen, FionaToSantiagoCoworker) into ContactToRelationship

!insert (ArtisticCollectiveNetwork, GlobalArtMovement) into AddressBookMadeOfContact
!insert (ArtisticCollectiveNetwork, ArtHavenAcademy) into AddressBookMadeOfContact
!insert (ArtisticCollectiveNetwork, SantiagoReyes) into AddressBookMadeOfContact
!insert (ArtisticCollectiveNetwork, FionaChen) 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 focuses on an emergency response team managing disaster relief logistics among various entities, such as government agencies, NGOs, and individual responders. This scenario showcases how overconstraints might surface in both relationships and the scope of contact roles, particularly related to roles of autonomy and overlapping jurisdictions.

### Instance Description

1. **AddressBook**
   - **Emergency Response Address Book**: Contains contacts crucial for managing disaster response and relief operations.

2. **Contacts**
   - **Government Agency (National Disaster Management Authority)**:
     - **Industry**: Government Agency
     - **Phone**: +1-555-0100
     - **Website**: www.ndma.gov
     - **Email**: admin@ndma.gov
     - **Addresses**:
       - **Address 1**: 
         - City: Washington, D.C.
         - HouseNr: 400
         - Street: Capital Blvd
     - **Relationships**: 
       - **NGO Partner**: BOSS (TARGET: NGO Partner)
       - **Responder Chief**: COWORKER (TARGET: Responder Chief)
       - **Logistics Firm**: COWORKER (TARGET: Logistics Firm)

   - **NGO Partner (Global Relief Network)**:
     - **Industry**: Non-Governmental Organization
     - **Phone**: +44-203-555667
     - **Website**: www.globalrelief.org
     - **Email**: partner@globalrelief.org
     - **Addresses**:
       - **Address 1**:
         - City: London
         - HouseNr: 120
         - Street: Aid Avenue
       - **Address 2**:
         - City: Nairobi
         - HouseNr: 17
         - Street: Hope Street
     - **Relationships**:
       - **Government Agency**: EMPLOYEE (TARGET: Government Agency)
       - **Responder Chief**: EMPLOYEE (TARGET: Responder Chief)

   - **Responder Chief (Jordan Nguyen)**:
     - **Title**: Chief Coordinator
     - **Phone**: +61-2-5551123
     - **Email**: j.nguyen@emergencyresponse.org
     - **Addresses**:
       - **Address 1**:
         - City: Sydney
         - HouseNr: 500
         - Street: Response Lane
     - **Relationships**:
       - **Logistics Firm**: BOSS (TARGET: Logistics Firm)

   - **Logistics Firm (Rapid Transport Co.)**:
     - **Industry**: Logistics
     - **Phone**: +91-80-5559990
     - **Website**: www.rapidtransport.in
     - **Email**: logistics@rapidtransport.in
     - **Addresses**:
       - **Address 1**:
         - City: Bangalore
         - HouseNr: 45
         - Street: Cargo Street

3. **Notes**
   - **Note for Government Agency**:
     - **Author**: Director Operations
     - **Time**: 2023-07-20
     - **Type**: MEETING
     - **Comment**: Coordinate cross-border relief logistics.
   - **Note for NGO Partner**:
     - **Author**: Logistics Coordinator
     - **Time**: 2023-07-22
     - **Type**: EMAIL
     - **Comment**: Status update on resource allocation.

### Overconstraint Analysis

- **Violation**: The current model assumes that entities have a clear cut and singular relationship path, yet this scenario presents overlapping and multifaceted interactions within the disaster response chain, such as multiple "BOSS" roles that conflict due to the intertwined nature of operations. Furthermore, the structured limit on note multiplicities does not reflect the frequent and varied communication needed in emergency settings over different channels.

- **Insight**: This instance demonstrates the necessity for more adaptable relationship designations given the inherent complexity of emergency management systems. Relationships should allow for pre-emptive and reactionary roles simultaneously, reflecting the nuanced control and cooperation necessary among diverse entities. Also, expanding permissible communication modes and frequency within notes would increase the model's practicality in recording real-time, multidimensional strategizing across relief networks.

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

!new Company('NationalDisasterManagementAuthority')
!NationalDisasterManagementAuthority.name := 'National Disaster Management Authority'
!NationalDisasterManagementAuthority.phone := '+1-555-0100'
!NationalDisasterManagementAuthority.website := 'www.ndma.gov'
!NationalDisasterManagementAuthority.email := 'admin@ndma.gov'
!NationalDisasterManagementAuthority.industry := 'Government Agency'

!new Address('NDMAAddress')
!NDMAAddress.city := 'Washington, D.C.'
!NDMAAddress.houseNr := '400'
!NDMAAddress.street := 'Capital Blvd'
!insert (NationalDisasterManagementAuthority, NDMAAddress) into ContactContainsAddress

!new Note('NDMANote1')
!NDMANote1.author := 'Director Operations'
!NDMANote1.time := Date('2023-07-20')
!NDMANote1.type := #MEETING
!NDMANote1.comment := 'Coordinate cross-border relief logistics.'
!insert (NationalDisasterManagementAuthority, NDMANote1) into ContactContainsNote

!new Company('GlobalReliefNetwork')
!GlobalReliefNetwork.name := 'Global Relief Network'
!GlobalReliefNetwork.phone := '+44-203-555667'
!GlobalReliefNetwork.website := 'www.globalrelief.org'
!GlobalReliefNetwork.email := 'partner@globalrelief.org'
!GlobalReliefNetwork.industry := 'Non-Governmental Organization'

!new Address('GlobalReliefAddress1')
!GlobalReliefAddress1.city := 'London'
!GlobalReliefAddress1.houseNr := '120'
!GlobalReliefAddress1.street := 'Aid Avenue'
!insert (GlobalReliefNetwork, GlobalReliefAddress1) into ContactContainsAddress

!new Address('GlobalReliefAddress2')
!GlobalReliefAddress2.city := 'Nairobi'
!GlobalReliefAddress2.houseNr := '17'
!GlobalReliefAddress2.street := 'Hope Street'
!insert (GlobalReliefNetwork, GlobalReliefAddress2) into ContactContainsAddress

!new Note('GlobalReliefNote1')
!GlobalReliefNote1.author := 'Logistics Coordinator'
!GlobalReliefNote1.time := Date('2023-07-22')
!GlobalReliefNote1.type := #EMAIL
!GlobalReliefNote1.comment := 'Status update on resource allocation.'
!insert (GlobalReliefNetwork, GlobalReliefNote1) into ContactContainsNote

!new Person('JordanNguyen')
!JordanNguyen.name := 'Jordan Nguyen'
!JordanNguyen.phone := '+61-2-5551123'
!JordanNguyen.email := 'j.nguyen@emergencyresponse.org'
!JordanNguyen.title := 'Chief Coordinator'

!new Address('JordanNguyenAddress')
!JordanNguyenAddress.city := 'Sydney'
!JordanNguyenAddress.houseNr := '500'
!JordanNguyenAddress.street := 'Response Lane'
!insert (JordanNguyen, JordanNguyenAddress) into ContactContainsAddress

!new Company('RapidTransportCo')
!RapidTransportCo.name := 'Rapid Transport Co.'
!RapidTransportCo.phone := '+91-80-5559990'
!RapidTransportCo.website := 'www.rapidtransport.in'
!RapidTransportCo.email := 'logistics@rapidtransport.in'
!RapidTransportCo.industry := 'Logistics'

!new Address('RapidTransportAddress')
!RapidTransportAddress.city := 'Bangalore'
!RapidTransportAddress.houseNr := '45'
!RapidTransportAddress.street := 'Cargo Street'
!insert (RapidTransportCo, RapidTransportAddress) into ContactContainsAddress

!new Relationship('NDMAToGlobalReliefBoss')
!NDMAToGlobalReliefBoss.type := #BOSS
!insert (NDMAToGlobalReliefBoss, GlobalReliefNetwork) into RelationshipToContact
!insert (NationalDisasterManagementAuthority, NDMAToGlobalReliefBoss) into ContactToRelationship

!new Relationship('NDMAToJordanCoworker')
!NDMAToJordanCoworker.type := #COWORKER
!insert (NDMAToJordanCoworker, JordanNguyen) into RelationshipToContact
!insert (NationalDisasterManagementAuthority, NDMAToJordanCoworker) into ContactToRelationship

!new Relationship('NDMAToRapidTransportCoworker')
!NDMAToRapidTransportCoworker.type := #COWORKER
!insert (NDMAToRapidTransportCoworker, RapidTransportCo) into RelationshipToContact
!insert (NationalDisasterManagementAuthority, NDMAToRapidTransportCoworker) into ContactToRelationship

!new Relationship('GlobalReliefToNDMAEmployee')
!GlobalReliefToNDMAEmployee.type := #EMPLOYEE
!insert (GlobalReliefToNDMAEmployee, NationalDisasterManagementAuthority) into RelationshipToContact
!insert (GlobalReliefNetwork, GlobalReliefToNDMAEmployee) into ContactToRelationship

!new Relationship('GlobalReliefToJordanEmployee')
!GlobalReliefToJordanEmployee.type := #EMPLOYEE
!insert (GlobalReliefToJordanEmployee, JordanNguyen) into RelationshipToContact
!insert (GlobalReliefNetwork, GlobalReliefToJordanEmployee) into ContactToRelationship

!new Relationship('JordanToRapidTransportBoss')
!JordanToRapidTransportBoss.type := #BOSS
!insert (JordanToRapidTransportBoss, RapidTransportCo) into RelationshipToContact
!insert (JordanNguyen, JordanToRapidTransportBoss) into ContactToRelationship

!insert (EmergencyResponseAddressBook, NationalDisasterManagementAuthority) into AddressBookMadeOfContact
!insert (EmergencyResponseAddressBook, GlobalReliefNetwork) into AddressBookMadeOfContact
!insert (EmergencyResponseAddressBook, JordanNguyen) into AddressBookMadeOfContact
!insert (EmergencyResponseAddressBook, RapidTransportCo) into AddressBookMadeOfContact
</object_model>