AddressBook / gen3

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: Intercontinental Contacts Directory

### Address Book
- **Name**: Intercontinental Contacts Directory

### Contacts

#### 1. Person Contact
- **Name**: Priya Nair
- **Phone**: +91-98123-45678
- **Website**: www.priyanair.in
- **Email**: priya.nair@consultant.in
- **Title**: Business Analyst

##### Notes for Priya Nair
1. **Note**
   - **Author**: Priya Nair
   - **Time**: "2023-01-05"
   - **Type**: CALL
   - **Comment**: Initial client requirement gathering for project "Asha".

##### Address for Priya Nair
- **City**: Mumbai
- **House Number**: 23D
- **Street**: Laxmi Nagar

##### Relationships for Priya Nair
1. **Relationship**
   - **Type**: COWORKER
   - **Target**: Johan Fredriksson

2. **Relationship**
   - **Type**: BOSS
   - **Target**: Mei Ling

#### 2. Company Contact
- **Name**: Pacific Mineral Exploration
- **Phone**: +61-2-9999-5555
- **Website**: www.pacificminerals.com.au
- **Email**: info@pacificminerals.com.au
- **Industry**: Mining

##### Notes for Pacific Mineral Exploration
- **Note**
  - **Author**: Li Wei
  - **Time**: "2023-03-15"
  - **Type**: MEETING
  - **Comment**: Annual environmental compliance review meeting.

##### Address for Pacific Mineral Exploration
1. **Address**
   - **City**: Sydney
   - **House Number**: 5
   - **Street**: George Street

2. **Address**
   - **City**: Perth
   - **House Number**: 101
   - **Street**: St Georges Terrace

#### 3. Person Contact
- **Name**: Johan Fredriksson
- **Phone**: +46-73-400-1112
- **Website**: www.fredriksolconsulting.se
- **Email**: johan.fredriksson@intermediate.com
- **Title**: Financial Advisor

##### Notes for Johan Fredriksson
- **Note**
  - **Author**: Johan Fredriksson
  - **Time**: "2023-09-05"
  - **Type**: EMAIL
  - **Comment**: Recommendations for optimizing investment strategies for the next fiscal year.

##### Address for Johan Fredriksson
- **City**: Stockholm
- **House Number**: 67
- **Street**: Östermalmstorg

##### Relationships for Johan Fredriksson
1. **Relationship**
   - **Type**: COWORKER
   - **Target**: Priya Nair

2. **Relationship**
   - **Type**: SUBDIVISION
   - **Target**: Pacific Mineral Exploration

#### 4. Person Contact
- **Name**: Mei Ling
- **Phone**: +86-10-6655-4422
- **Website**: www.meilingart.com.cn
- **Email**: mei.ling@artisticvision.cn
- **Title**: Creative Director

##### Notes for Mei Ling
- **Note**
  - **Author**: Mei Ling
  - **Time**: "2023-06-20"
  - **Type**: MEETING
  - **Comment**: Brainstorming session for the upcoming digital art exhibition.

##### Address for Mei Ling
- **City**: Beijing
- **House Number**: 3-5
- **Street**: Wangfujing

##### Relationships for Mei Ling
- **Relationship**
  - **Type**: EMPLOYEE
  - **Target**: Priya Nair

### Relationships

- **Priya Nair** and **Johan Fredriksson** are **COWORKERS**.
- **Priya Nair** manages **Mei Ling** as her **BOSS**.
- **Mei Ling** reports to **Priya Nair** as an **EMPLOYEE**.
- **Johan Fredriksson** manages a **SUBDIVISION**, which includes **Pacific Mineral Exploration**.

This instance showcases a multi-continental composition with environments ranging from consulting and finance to mining and creative industries, illustrating diverse professional networks and international collaborations. It features different combinations of locations and business sectors to ensure a rich, varied exploration of global business dynamics.

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

!new Person('PriyaNair')
!PriyaNair.name := 'Priya Nair'
!PriyaNair.phone := '+91-98123-45678'
!PriyaNair.website := 'www.priyanair.in'
!PriyaNair.email := 'priya.nair@consultant.in'
!PriyaNair.title := 'Business Analyst'

!new Address('PriyaNairAddress')
!PriyaNairAddress.city := 'Mumbai'
!PriyaNairAddress.houseNr := '23D'
!PriyaNairAddress.street := 'Laxmi Nagar'
!insert (PriyaNair, PriyaNairAddress) into ContactContainsAddress

!new Note('PriyaNairNote1')
!PriyaNairNote1.author := 'Priya Nair'
!PriyaNairNote1.time := Date('2023-01-05')
!PriyaNairNote1.type := #CALL
!PriyaNairNote1.comment := 'Initial client requirement gathering for project "Asha".'
!insert (PriyaNair, PriyaNairNote1) into ContactContainsNote

!new Company('PacificMineralExploration')
!PacificMineralExploration.name := 'Pacific Mineral Exploration'
!PacificMineralExploration.phone := '+61-2-9999-5555'
!PacificMineralExploration.website := 'www.pacificminerals.com.au'
!PacificMineralExploration.email := 'info@pacificminerals.com.au'
!PacificMineralExploration.industry := 'Mining'

!new Address('PacificMineralAddress1')
!PacificMineralAddress1.city := 'Sydney'
!PacificMineralAddress1.houseNr := '5'
!PacificMineralAddress1.street := 'George Street'
!insert (PacificMineralExploration, PacificMineralAddress1) into ContactContainsAddress

!new Address('PacificMineralAddress2')
!PacificMineralAddress2.city := 'Perth'
!PacificMineralAddress2.houseNr := '101'
!PacificMineralAddress2.street := 'St Georges Terrace'
!insert (PacificMineralExploration, PacificMineralAddress2) into ContactContainsAddress

!new Note('PacificMineralNote1')
!PacificMineralNote1.author := 'Li Wei'
!PacificMineralNote1.time := Date('2023-03-15')
!PacificMineralNote1.type := #MEETING
!PacificMineralNote1.comment := 'Annual environmental compliance review meeting.'
!insert (PacificMineralExploration, PacificMineralNote1) into ContactContainsNote

!new Person('JohanFredriksson')
!JohanFredriksson.name := 'Johan Fredriksson'
!JohanFredriksson.phone := '+46-73-400-1112'
!JohanFredriksson.website := 'www.fredriksolconsulting.se'
!JohanFredriksson.email := 'johan.fredriksson@intermediate.com'
!JohanFredriksson.title := 'Financial Advisor'

!new Address('JohanFredrikssonAddress')
!JohanFredrikssonAddress.city := 'Stockholm'
!JohanFredrikssonAddress.houseNr := '67'
!JohanFredrikssonAddress.street := 'Östermalmstorg'
!insert (JohanFredriksson, JohanFredrikssonAddress) into ContactContainsAddress

!new Note('JohanFredrikssonNote1')
!JohanFredrikssonNote1.author := 'Johan Fredriksson'
!JohanFredrikssonNote1.time := Date('2023-09-05')
!JohanFredrikssonNote1.type := #EMAIL
!JohanFredrikssonNote1.comment := 'Recommendations for optimizing investment strategies for the next fiscal year.'
!insert (JohanFredriksson, JohanFredrikssonNote1) into ContactContainsNote

!new Person('MeiLing')
!MeiLing.name := 'Mei Ling'
!MeiLing.phone := '+86-10-6655-4422'
!MeiLing.website := 'www.meilingart.com.cn'
!MeiLing.email := 'mei.ling@artisticvision.cn'
!MeiLing.title := 'Creative Director'

!new Address('MeiLingAddress')
!MeiLingAddress.city := 'Beijing'
!MeiLingAddress.houseNr := '3-5'
!MeiLingAddress.street := 'Wangfujing'
!insert (MeiLing, MeiLingAddress) into ContactContainsAddress

!new Note('MeiLingNote1')
!MeiLingNote1.author := 'Mei Ling'
!MeiLingNote1.time := Date('2023-06-20')
!MeiLingNote1.type := #MEETING
!MeiLingNote1.comment := 'Brainstorming session for the upcoming digital art exhibition.'
!insert (MeiLing, MeiLingNote1) into ContactContainsNote

!new Relationship('PriyaToJohanCoworker')
!PriyaToJohanCoworker.type := #COWORKER
!insert (PriyaToJohanCoworker, JohanFredriksson) into RelationshipToContact
!insert (PriyaNair, PriyaToJohanCoworker) into ContactToRelationship

!new Relationship('PriyaToMeiBoss')
!PriyaToMeiBoss.type := #BOSS
!insert (PriyaToMeiBoss, MeiLing) into RelationshipToContact
!insert (PriyaNair, PriyaToMeiBoss) into ContactToRelationship

!new Relationship('JohanToPriyaCoworker')
!JohanToPriyaCoworker.type := #COWORKER
!insert (JohanToPriyaCoworker, PriyaNair) into RelationshipToContact
!insert (JohanFredriksson, JohanToPriyaCoworker) into ContactToRelationship

!new Relationship('JohanToPacificSubdivision')
!JohanToPacificSubdivision.type := #SUBDIVISION
!insert (JohanToPacificSubdivision, PacificMineralExploration) into RelationshipToContact
!insert (JohanFredriksson, JohanToPacificSubdivision) into ContactToRelationship

!new Relationship('MeiToPriyaEmployee')
!MeiToPriyaEmployee.type := #EMPLOYEE
!insert (MeiToPriyaEmployee, PriyaNair) into RelationshipToContact
!insert (MeiLing, MeiToPriyaEmployee) into ContactToRelationship

!insert (IntercontinentalContactsDirectory, PriyaNair) into AddressBookMadeOfContact
!insert (IntercontinentalContactsDirectory, PacificMineralExploration) into AddressBookMadeOfContact
!insert (IntercontinentalContactsDirectory, JohanFredriksson) into AddressBookMadeOfContact
!insert (IntercontinentalContactsDirectory, MeiLing) 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: "Artistic Network Address Book"

### Address Book
- **AddressBook**: "Artistic Network Address Book"
  - This address book is designed for maintaining connections among artists and galleries across different regions focusing on cultural and artistic collaboration.

### Contacts
- **Contact 1**: "Sculptors Guild"
  - **Type**: Company
  - **Attributes**:
    - Name: Sculptors Guild
    - Phone: +1-212-555-0234
    - Website: www.sculptorsguild.org
    - Email: contact@sculptorsguild.org
    - Industry: Arts and Crafts
  - **Addresses**:
    - (Boundary consideration with no addresses)

- **Contact 2**: "Marta Rivera"
  - **Type**: Person
  - **Attributes**:
    - Name: Marta Rivera
    - Phone: +34-91-123-4567
    - Website: www.martarivera.art
    - Email: marta@rivera.art
    - Title: Renowned Painter
  - **Addresses**:
    - Address 1:
      - City: Madrid
      - HouseNr: 88
      - Street: Calle de Alcalá

- **Contact 3**: "EastEnd Gallery"
  - **Type**: Company
  - **Attributes**:
    - Name: EastEnd Gallery
    - Phone: +49-30-555-0170
    - Website: www.eastendgallery.de
    - Email: info@eastendgallery.de
    - Industry: Art Gallery
  - **Addresses**:
    - Address 1:
      - City: Berlin
      - HouseNr: 44
      - Street: Kurfürstendamm
    - Address 2:
      - City: Hamburg
      - HouseNr: 10
      - Street: Kunstallee

- **Contact 4**: "Julien Monet"
  - **Type**: Person
  - **Attributes**:
    - Name: Julien Monet
    - Phone: +33-1-555-0130
    - Website: www.julienmonet.eu
    - Email: julien@monetstudio.fr
    - Title: Art Critic
  - **Addresses**:
    - (Boundary consideration with no addresses)
  - **Notes**:
    - Note 1:
      - Author: Julien Monet
      - Time: "2023-06-12"
      - Type: EMAIL
      - Comment: Offered critique and insights on the new exhibit.

### Relationships
- **Relationship 1**: Between "EastEnd Gallery" and "Marta Rivera"
  - **Type**: SUBDIVISION
  - Target: Marta Rivera

- **Relationship 2**: Between "Julien Monet" and "EastEnd Gallery"
  - **Type**: COWORKER
  - Target: EastEnd Gallery

- **Relationship 3**: Between "Sculptors Guild" and "Julien Monet"
  - **Type**: EMPLOYEE
  - Target: Julien Monet

### Boundary Considerations
- Inclusion of various art-oriented entities emphasizing cultural diversity with entities based in Madrid, Berlin, and Paris, all common cultural centers.
- "Sculptors Guild" and "Julien Monet" exploring scenarios with no physical address to emphasize digital networking in the arts.
- Different roles like artists, galleries, and art critics interrelate, highlighting the multi-faceted nature of the artistic community.

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

!new Company('SculptorsGuild')
!SculptorsGuild.name := 'Sculptors Guild'
!SculptorsGuild.phone := '+1-212-555-0234'
!SculptorsGuild.website := 'www.sculptorsguild.org'
!SculptorsGuild.email := 'contact@sculptorsguild.org'
!SculptorsGuild.industry := 'Arts and Crafts'

!new Person('MartaRivera')
!MartaRivera.name := 'Marta Rivera'
!MartaRivera.phone := '+34-91-123-4567'
!MartaRivera.website := 'www.martarivera.art'
!MartaRivera.email := 'marta@rivera.art'
!MartaRivera.title := 'Renowned Painter'

!new Address('MartaRiveraAddress')
!MartaRiveraAddress.city := 'Madrid'
!MartaRiveraAddress.houseNr := '88'
!MartaRiveraAddress.street := 'Calle de Alcalá'
!insert (MartaRivera, MartaRiveraAddress) into ContactContainsAddress

!new Company('EastEndGallery')
!EastEndGallery.name := 'EastEnd Gallery'
!EastEndGallery.phone := '+49-30-555-0170'
!EastEndGallery.website := 'www.eastendgallery.de'
!EastEndGallery.email := 'info@eastendgallery.de'
!EastEndGallery.industry := 'Art Gallery'

!new Address('EastEndGalleryAddress1')
!EastEndGalleryAddress1.city := 'Berlin'
!EastEndGalleryAddress1.houseNr := '44'
!EastEndGalleryAddress1.street := 'Kurfürstendamm'
!insert (EastEndGallery, EastEndGalleryAddress1) into ContactContainsAddress

!new Address('EastEndGalleryAddress2')
!EastEndGalleryAddress2.city := 'Hamburg'
!EastEndGalleryAddress2.houseNr := '10'
!EastEndGalleryAddress2.street := 'Kunstallee'
!insert (EastEndGallery, EastEndGalleryAddress2) into ContactContainsAddress

!new Person('JulienMonet')
!JulienMonet.name := 'Julien Monet'
!JulienMonet.phone := '+33-1-555-0130'
!JulienMonet.website := 'www.julienmonet.eu'
!JulienMonet.email := 'julien@monetstudio.fr'
!JulienMonet.title := 'Art Critic'

!new Note('JulienMonetNote1')
!JulienMonetNote1.author := 'Julien Monet'
!JulienMonetNote1.time := Date('2023-06-12')
!JulienMonetNote1.type := #EMAIL
!JulienMonetNote1.comment := 'Offered critique and insights on the new exhibit.'
!insert (JulienMonet, JulienMonetNote1) into ContactContainsNote

!new Relationship('EastEndGalleryToMartaSubdivision')
!EastEndGalleryToMartaSubdivision.type := #SUBDIVISION
!insert (EastEndGalleryToMartaSubdivision, MartaRivera) into RelationshipToContact
!insert (EastEndGallery, EastEndGalleryToMartaSubdivision) into ContactToRelationship

!new Relationship('JulienToEastEndCoworker')
!JulienToEastEndCoworker.type := #COWORKER
!insert (JulienToEastEndCoworker, EastEndGallery) into RelationshipToContact
!insert (JulienMonet, JulienToEastEndCoworker) into ContactToRelationship

!new Relationship('SculptorsToJulienEmployee')
!SculptorsToJulienEmployee.type := #EMPLOYEE
!insert (SculptorsToJulienEmployee, JulienMonet) into RelationshipToContact
!insert (SculptorsGuild, SculptorsToJulienEmployee) into ContactToRelationship

!insert (ArtisticNetworkAddressBook, SculptorsGuild) into AddressBookMadeOfContact
!insert (ArtisticNetworkAddressBook, MartaRivera) into AddressBookMadeOfContact
!insert (ArtisticNetworkAddressBook, EastEndGallery) into AddressBookMadeOfContact
!insert (ArtisticNetworkAddressBook, JulienMonet) 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: "Cultural Exchange Hub"

This address book, called "Cultural Exchange Hub," brings together a rich array of contacts from various cultural organizations and artists involved in international cultural exchanges.

#### Contacts

1. **Contact 1 - Person**
   - **Name**: Sarah Liu
   - **Phone**: +86 10 6677 8899
   - **Website**: www.sarahliuart.com
   - **Email**: sarah.liu@artspaces.cn
   - **Title**: Curator

   - **Addresses**:
     - **1.1 Address**:
       - **City**: Beijing
       - **Street**: Art District
       - **House Number**: 72

   - **Notes**:
     - **1.1 Note**:
       - **Author**: Sarah Liu
       - **Time**: "2023-09-12"
       - **Type**: MEETING
       - **Comment**: "Visited the European Art & Cultural Expo to explore potential collaborations."

     - **1.2 Note**:
       - **Author**: Sarah Liu
       - **Time**: "2023-09-20"
       - **Type**: EMAIL
       - **Comment**: "Discussed arrangements for the contemporary art exhibit with international partners."

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

2. **Contact 2 - Person**
   - **Name**: Carlos Rovira
   - **Phone**: +54 11 4966 7722
   - **Website**: www.carlosrovira.com
   - **Email**: carlosrovira@aol.com
   - **Title**: Cultural Attaché

   - **Addresses**:
     - **2.1 Address**:
       - **City**: Buenos Aires
       - **Street**: Libertador Avenue
       - **House Number**: 999

   - **Notes**:
     - **2.1 Note**:
       - **Author**: Carlos Rovira
       - **Time**: "2023-10-05"
       - **Type**: CALL
       - **Comment**: "Phone call with local artists about the upcoming cultural exchange program."

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

3. **Contact 3 - Company**
   - **Name**: Global Art Exchange
   - **Phone**: +44 20 3004 5678
   - **Website**: www.globalartexchange.org
   - **Email**: admin@globalartexchange.org
   - **Industry**: Arts and Culture

   - **Addresses**:
     - **3.1 Address**:
       - **City**: London
       - **Street**: Culture Lane
       - **House Number**: 85

   - **Notes**:
     - **3.1 Note**:
       - **Author**: Global Art Exchange
       - **Time**: "2023-10-12"
       - **Type**: MEETING
       - **Comment**: "Strategic planning meeting for next year's international cultural festival."

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

4. **Contact 4 - Company**
   - **Name**: Cultural Horizons
   - **Phone**: +81 3 1234 7890
   - **Website**: www.culturalhorizons.jp
   - **Email**: info@culturalhorizons.jp
   - **Industry**: Art and Heritage

   - **Addresses**:
     - **4.1 Address**:
       - **City**: Tokyo
       - **Street**: Artisans Lane
       - **House Number**: 58

   - **Notes**:
     - **4.1 Note**:
       - **Author**: Cultural Horizons
       - **Time**: "2023-10-20"
       - **Type**: EMAIL
       - **Comment**: "Coordinated the preparation of exhibits for the Global Art Exchange partnership."

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

### Invariant Check
- **DifferentSourceTarget**: All relationship targets are distinct from their source entities, ensuring no self-referential relationships exist.

This instance captures the cultural sector's dynamic interconnectedness, including individuals and organizations facilitating global cultural exchanges, highlighting the diversity of participants from different parts of the world committed to promoting arts and heritage.

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

!new Person('SarahLiu')
!SarahLiu.name := 'Sarah Liu'
!SarahLiu.phone := '+86 10 6677 8899'
!SarahLiu.website := 'www.sarahliuart.com'
!SarahLiu.email := 'sarah.liu@artspaces.cn'
!SarahLiu.title := 'Curator'

!new Address('SarahLiuAddress')
!SarahLiuAddress.city := 'Beijing'
!SarahLiuAddress.street := 'Art District'
!SarahLiuAddress.houseNr := '72'
!insert (SarahLiu, SarahLiuAddress) into ContactContainsAddress

!new Note('SarahLiuNote1')
!SarahLiuNote1.author := 'Sarah Liu'
!SarahLiuNote1.time := Date('2023-09-12')
!SarahLiuNote1.type := #MEETING
!SarahLiuNote1.comment := 'Visited the European Art & Cultural Expo to explore potential collaborations.'
!insert (SarahLiu, SarahLiuNote1) into ContactContainsNote

!new Note('SarahLiuNote2')
!SarahLiuNote2.author := 'Sarah Liu'
!SarahLiuNote2.time := Date('2023-09-20')
!SarahLiuNote2.type := #EMAIL
!SarahLiuNote2.comment := 'Discussed arrangements for the contemporary art exhibit with international partners.'
!insert (SarahLiu, SarahLiuNote2) into ContactContainsNote

!new Person('CarlosRovira')
!CarlosRovira.name := 'Carlos Rovira'
!CarlosRovira.phone := '+54 11 4966 7722'
!CarlosRovira.website := 'www.carlosrovira.com'
!CarlosRovira.email := 'carlosrovira@aol.com'
!CarlosRovira.title := 'Cultural Attaché'

!new Address('CarlosRoviraAddress')
!CarlosRoviraAddress.city := 'Buenos Aires'
!CarlosRoviraAddress.street := 'Libertador Avenue'
!CarlosRoviraAddress.houseNr := '999'
!insert (CarlosRovira, CarlosRoviraAddress) into ContactContainsAddress

!new Note('CarlosRoviraNote1')
!CarlosRoviraNote1.author := 'Carlos Rovira'
!CarlosRoviraNote1.time := Date('2023-10-05')
!CarlosRoviraNote1.type := #CALL
!CarlosRoviraNote1.comment := 'Phone call with local artists about the upcoming cultural exchange program.'
!insert (CarlosRovira, CarlosRoviraNote1) into ContactContainsNote

!new Company('GlobalArtExchange')
!GlobalArtExchange.name := 'Global Art Exchange'
!GlobalArtExchange.phone := '+44 20 3004 5678'
!GlobalArtExchange.website := 'www.globalartexchange.org'
!GlobalArtExchange.email := 'admin@globalartexchange.org'
!GlobalArtExchange.industry := 'Arts and Culture'

!new Address('GlobalArtExchangeAddress')
!GlobalArtExchangeAddress.city := 'London'
!GlobalArtExchangeAddress.street := 'Culture Lane'
!GlobalArtExchangeAddress.houseNr := '85'
!insert (GlobalArtExchange, GlobalArtExchangeAddress) into ContactContainsAddress

!new Note('GlobalArtExchangeNote1')
!GlobalArtExchangeNote1.author := 'Global Art Exchange'
!GlobalArtExchangeNote1.time := Date('2023-10-12')
!GlobalArtExchangeNote1.type := #MEETING
!GlobalArtExchangeNote1.comment := 'Strategic planning meeting for next year\'s international cultural festival.'
!insert (GlobalArtExchange, GlobalArtExchangeNote1) into ContactContainsNote

!new Company('CulturalHorizons')
!CulturalHorizons.name := 'Cultural Horizons'
!CulturalHorizons.phone := '+81 3 1234 7890'
!CulturalHorizons.website := 'www.culturalhorizons.jp'
!CulturalHorizons.email := 'info@culturalhorizons.jp'
!CulturalHorizons.industry := 'Art and Heritage'

!new Address('CulturalHorizonsAddress')
!CulturalHorizonsAddress.city := 'Tokyo'
!CulturalHorizonsAddress.street := 'Artisans Lane'
!CulturalHorizonsAddress.houseNr := '58'
!insert (CulturalHorizons, CulturalHorizonsAddress) into ContactContainsAddress

!new Note('CulturalHorizonsNote1')
!CulturalHorizonsNote1.author := 'Cultural Horizons'
!CulturalHorizonsNote1.time := Date('2023-10-20')
!CulturalHorizonsNote1.type := #EMAIL
!CulturalHorizonsNote1.comment := 'Coordinated the preparation of exhibits for the Global Art Exchange partnership.'
!insert (CulturalHorizons, CulturalHorizonsNote1) into ContactContainsNote

!new Relationship('SarahToGlobalArtEmployee')
!SarahToGlobalArtEmployee.type := #EMPLOYEE
!insert (SarahToGlobalArtEmployee, GlobalArtExchange) into RelationshipToContact
!insert (SarahLiu, SarahToGlobalArtEmployee) into ContactToRelationship

!new Relationship('CarlosToGlobalArtCoworker')
!CarlosToGlobalArtCoworker.type := #COWORKER
!insert (CarlosToGlobalArtCoworker, GlobalArtExchange) into RelationshipToContact
!insert (CarlosRovira, CarlosToGlobalArtCoworker) into ContactToRelationship

!new Relationship('GlobalArtToCulturalSubdivision')
!GlobalArtToCulturalSubdivision.type := #SUBDIVISION
!insert (GlobalArtToCulturalSubdivision, CulturalHorizons) into RelationshipToContact
!insert (GlobalArtExchange, GlobalArtToCulturalSubdivision) into ContactToRelationship

!new Relationship('GlobalArtToSarahBoss')
!GlobalArtToSarahBoss.type := #BOSS
!insert (GlobalArtToSarahBoss, SarahLiu) into RelationshipToContact
!insert (GlobalArtExchange, GlobalArtToSarahBoss) into ContactToRelationship

!new Relationship('CulturalToGlobalArtSubdivision')
!CulturalToGlobalArtSubdivision.type := #SUBDIVISION
!insert (CulturalToGlobalArtSubdivision, GlobalArtExchange) into RelationshipToContact
!insert (CulturalHorizons, CulturalToGlobalArtSubdivision) into ContactToRelationship

!new Relationship('CulturalToCarlosBoss')
!CulturalToCarlosBoss.type := #BOSS
!insert (CulturalToCarlosBoss, CarlosRovira) into RelationshipToContact
!insert (CulturalHorizons, CulturalToCarlosBoss) into ContactToRelationship

!insert (CulturalExchangeHub, SarahLiu) into AddressBookMadeOfContact
!insert (CulturalExchangeHub, CarlosRovira) into AddressBookMadeOfContact
!insert (CulturalExchangeHub, GlobalArtExchange) into AddressBookMadeOfContact
!insert (CulturalExchangeHub, CulturalHorizons) 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 dedicated to a multinational legal firm with a complex web of partnerships and competitive relationships across distinct continental operations. The instance particularly features intricate dynamics within the legal and corporate advisory realms, including distinctive relationships and high-level notes reflecting strategic interactions.

### Address Book Instance
- **AddressBook: Global Legal Network Directory**

### Contacts
1. **Contact (Company)**
   - **Name**: Meyer & Chang Legal Advisors
   - **Phone**: +61-2-90348888
   - **Website**: www.meyerchanglaw.au
   - **Email**: contact@meyerchanglaw.au
   - **Industry**: Legal Services
   - **Notes**:
     - **Note 1**:
       - **Author**: Justine Meyer
       - **Time**: "2023-07-02T09:00:00"
       - **Type**: MEETING
       - **Comment**: Discussed merger with Lin & Partners.
   - **Address**:
     - **City**: Sydney
     - **HouseNr**: 23
     - **Street**: Barrister Lane
   - **Relationships**:
     - **To**: Lin & Partners (Relation: COWORKER)
     - **To**: Prof. Raphael Taylor (Relation: SUBDIVISION)

2. **Contact (Company)**
   - **Name**: Lin & Partners
   - **Phone**: +852-25387890
   - **Website**: www.linpartners.hk
   - **Email**: contact@linpartners.hk
   - **Industry**: Corporate Advisory
   - **Notes**:
     - **Note 1**:
       - **Author**: Zheng Lin
       - **Time**: "2023-08-12T10:30:00"
       - **Type**: EMAIL
       - **Comment**: Strategic partnership proposal with Meyer & Chang.
   - **Address**:
     - **City**: Hong Kong
     - **HouseNr**: 88
     - **Street**: Financial Plaza
   - **Relationships**:
     - **To**: Meyer & Chang Legal Advisors (Relation: COWORKER)
     - **To**: Prof. Raphael Taylor (Relation: BOSS)

3. **Contact (Person)**
   - **Name**: Prof. Raphael Taylor
   - **Phone**: +44-20-78594567
   - **Website**: www.taylorlegalresearch.org
   - **Email**: r.taylor@edu.ac.uk
   - **Title**: Head of International Law Division
   - **Notes**:
     - **Note 1**:
       - **Author**: Prof. Raphael Taylor
       - **Time**: "2023-06-20T14:00:00"
       - **Type**: MEETING
       - **Comment**: Attended international law convention in Geneva.
     - **Note 2**:
       - **Author**: Prof. Raphael Taylor
       - **Time**: "2023-05-19T11:45:00"
       - **Type**: CALL
       - **Comment**: Conference call on regulatory compliance with EU partners.
   - **Address**:
     - **City**: London
     - **HouseNr**: 15
     - **Street**: Legal Research Avenue
   - **Relationships**:
     - **To**: Meyer & Chang Legal Advisors (Relation: SUBDIVISION)
     - **To**: Lin & Partners (Relation: EMPLOYEE)

4. **Contact (Person)**
   - **Name**: Alexander Davis
   - **Phone**: +1-212-5550987
   - **Website**: www.davislegaladvisor.com
   - **Email**: alex.davis@law.com
   - **Title**: Senior Corporate Counsel
   - **Notes**:
     - **Note 1**:
       - **Author**: Alexander Davis
       - **Time**: "2023-07-15T16:30:00"
       - **Type**: MEETING
       - **Comment**: New York office quarterly review.
   - **Address**:
     - **City**: New York
     - **HouseNr**: 101
     - **Street**: Madison Avenue
   - **Relationships**:
     - **To**: Lin & Partners (Relation: COWORKER)
     - **To**: Prof. Raphael Taylor (Relation: SUBDIVISION)

### Edge Case Details
- **Intercompany Dynamics**: The instance showcases strong intercompany collaborations and complicated subdivisions between companies and key individuals.
- **Global Scope**: Multinational impact with operations and communications from Australia to the UK, Hong Kong to the USA, reflecting diverse jurisdictional nuances.
- **Complex Reporting Structure**: Prof. Raphael Taylor, based in the academic sector, plays a significant corporate role reflected through layered relationships across multiple firms.
- **Highly Detailed Notes**: Each major player makes critical, strategic decisions documented through comprehensive notes, highlighting a scenario unlikely in smaller-scale operations.

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

!new Company('MeyerAndChang')
!MeyerAndChang.name := 'Meyer & Chang Legal Advisors'
!MeyerAndChang.phone := '+61-2-90348888'
!MeyerAndChang.website := 'www.meyerchanglaw.au'
!MeyerAndChang.email := 'contact@meyerchanglaw.au'
!MeyerAndChang.industry := 'Legal Services'

!new Address('MeyerAndChangAddress')
!MeyerAndChangAddress.city := 'Sydney'
!MeyerAndChangAddress.houseNr := '23'
!MeyerAndChangAddress.street := 'Barrister Lane'
!insert (MeyerAndChang, MeyerAndChangAddress) into ContactContainsAddress

!new Note('MeyerAndChangNote1')
!MeyerAndChangNote1.author := 'Justine Meyer'
!MeyerAndChangNote1.time := Date('2023-07-02T09:00:00')
!MeyerAndChangNote1.type := #MEETING
!MeyerAndChangNote1.comment := 'Discussed merger with Lin & Partners.'
!insert (MeyerAndChang, MeyerAndChangNote1) into ContactContainsNote

!new Company('LinAndPartners')
!LinAndPartners.name := 'Lin & Partners'
!LinAndPartners.phone := '+852-25387890'
!LinAndPartners.website := 'www.linpartners.hk'
!LinAndPartners.email := 'contact@linpartners.hk'
!LinAndPartners.industry := 'Corporate Advisory'

!new Address('LinAndPartnersAddress')
!LinAndPartnersAddress.city := 'Hong Kong'
!LinAndPartnersAddress.houseNr := '88'
!LinAndPartnersAddress.street := 'Financial Plaza'
!insert (LinAndPartners, LinAndPartnersAddress) into ContactContainsAddress

!new Note('LinAndPartnersNote1')
!LinAndPartnersNote1.author := 'Zheng Lin'
!LinAndPartnersNote1.time := Date('2023-08-12T10:30:00')
!LinAndPartnersNote1.type := #EMAIL
!LinAndPartnersNote1.comment := 'Strategic partnership proposal with Meyer & Chang.'
!insert (LinAndPartners, LinAndPartnersNote1) into ContactContainsNote

!new Person('ProfRaphaelTaylor')
!ProfRaphaelTaylor.name := 'Prof. Raphael Taylor'
!ProfRaphaelTaylor.phone := '+44-20-78594567'
!ProfRaphaelTaylor.website := 'www.taylorlegalresearch.org'
!ProfRaphaelTaylor.email := 'r.taylor@edu.ac.uk'
!ProfRaphaelTaylor.title := 'Head of International Law Division'

!new Address('RaphaelTaylorAddress')
!RaphaelTaylorAddress.city := 'London'
!RaphaelTaylorAddress.houseNr := '15'
!RaphaelTaylorAddress.street := 'Legal Research Avenue'
!insert (ProfRaphaelTaylor, RaphaelTaylorAddress) into ContactContainsAddress

!new Note('RaphaelTaylorNote1')
!RaphaelTaylorNote1.author := 'Prof. Raphael Taylor'
!RaphaelTaylorNote1.time := Date('2023-06-20T14:00:00')
!RaphaelTaylorNote1.type := #MEETING
!RaphaelTaylorNote1.comment := 'Attended international law convention in Geneva.'
!insert (ProfRaphaelTaylor, RaphaelTaylorNote1) into ContactContainsNote

!new Note('RaphaelTaylorNote2')
!RaphaelTaylorNote2.author := 'Prof. Raphael Taylor'
!RaphaelTaylorNote2.time := Date('2023-05-19T11:45:00')
!RaphaelTaylorNote2.type := #CALL
!RaphaelTaylorNote2.comment := 'Conference call on regulatory compliance with EU partners.'
!insert (ProfRaphaelTaylor, RaphaelTaylorNote2) into ContactContainsNote

!new Person('AlexanderDavis')
!AlexanderDavis.name := 'Alexander Davis'
!AlexanderDavis.phone := '+1-212-5550987'
!AlexanderDavis.website := 'www.davislegaladvisor.com'
!AlexanderDavis.email := 'alex.davis@law.com'
!AlexanderDavis.title := 'Senior Corporate Counsel'

!new Address('AlexanderDavisAddress')
!AlexanderDavisAddress.city := 'New York'
!AlexanderDavisAddress.houseNr := '101'
!AlexanderDavisAddress.street := 'Madison Avenue'
!insert (AlexanderDavis, AlexanderDavisAddress) into ContactContainsAddress

!new Note('AlexanderDavisNote1')
!AlexanderDavisNote1.author := 'Alexander Davis'
!AlexanderDavisNote1.time := Date('2023-07-15T16:30:00')
!AlexanderDavisNote1.type := #MEETING
!AlexanderDavisNote1.comment := 'New York office quarterly review.'
!insert (AlexanderDavis, AlexanderDavisNote1) into ContactContainsNote

!new Relationship('MeyerToLinCoworker')
!MeyerToLinCoworker.type := #COWORKER
!insert (MeyerToLinCoworker, LinAndPartners) into RelationshipToContact
!insert (MeyerAndChang, MeyerToLinCoworker) into ContactToRelationship

!new Relationship('MeyerToRaphaelSubdivision')
!MeyerToRaphaelSubdivision.type := #SUBDIVISION
!insert (MeyerToRaphaelSubdivision, ProfRaphaelTaylor) into RelationshipToContact
!insert (MeyerAndChang, MeyerToRaphaelSubdivision) into ContactToRelationship

!new Relationship('LinToMeyerCoworker')
!LinToMeyerCoworker.type := #COWORKER
!insert (LinToMeyerCoworker, MeyerAndChang) into RelationshipToContact
!insert (LinAndPartners, LinToMeyerCoworker) into ContactToRelationship

!new Relationship('LinToRaphaelBoss')
!LinToRaphaelBoss.type := #BOSS
!insert (LinToRaphaelBoss, ProfRaphaelTaylor) into RelationshipToContact
!insert (LinAndPartners, LinToRaphaelBoss) into ContactToRelationship

!new Relationship('RaphaelToMeyerSubdivision')
!RaphaelToMeyerSubdivision.type := #SUBDIVISION
!insert (RaphaelToMeyerSubdivision, MeyerAndChang) into RelationshipToContact
!insert (ProfRaphaelTaylor, RaphaelToMeyerSubdivision) into ContactToRelationship

!new Relationship('RaphaelToLinEmployee')
!RaphaelToLinEmployee.type := #EMPLOYEE
!insert (RaphaelToLinEmployee, LinAndPartners) into RelationshipToContact
!insert (ProfRaphaelTaylor, RaphaelToLinEmployee) into ContactToRelationship

!new Relationship('AlexToLinCoworker')
!AlexToLinCoworker.type := #COWORKER
!insert (AlexToLinCoworker, LinAndPartners) into RelationshipToContact
!insert (AlexanderDavis, AlexToLinCoworker) into ContactToRelationship

!new Relationship('AlexToRaphaelSubdivision')
!AlexToRaphaelSubdivision.type := #SUBDIVISION
!insert (AlexToRaphaelSubdivision, ProfRaphaelTaylor) into RelationshipToContact
!insert (AlexanderDavis, AlexToRaphaelSubdivision) into ContactToRelationship

!insert (GlobalLegalNetworkDirectory, MeyerAndChang) into AddressBookMadeOfContact
!insert (GlobalLegalNetworkDirectory, LinAndPartners) into AddressBookMadeOfContact
!insert (GlobalLegalNetworkDirectory, ProfRaphaelTaylor) into AddressBookMadeOfContact
!insert (GlobalLegalNetworkDirectory, AlexanderDavis) into AddressBookMadeOfContact
</object_model>

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

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

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

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

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

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

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

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

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

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

<output_format>
Structure your response exactly as follows:

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

<examples>
Example 1:
Input:

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

Output:

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


Example 2:
Input:

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

Output:

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


Example 3:
Input:

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

Output:

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

</examples>

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

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

### Scenario Overview
This instance involves an academic research collaboration project where multiple universities and individual researchers are coordinating on an international scale. The focus is on the constraints around the diversity and multiplicity of relationships and addresses, exposing potential overconstraints in documenting contacts with multiple roles in a decentralized research setup.

### Instance Description

1. **AddressBook**
   - **Research Collaboration Address Book**: This address book contains all the contacts relevant to the academic research collaboration.

2. **Contacts**
   - **University A (GlobalTech University)**:
     - **Industry**: Education
     - **Phone**: +1-617-555-6789
     - **Website**: www.globaltech.edu
     - **Email**: info@globaltech.edu
     - **Addresses**:
       - **Address 1**: 
         - City: Boston
         - HouseNr: 50
         - Street: College Road
       - **Address 2**:
         - City: New York
         - HouseNr: 130
         - Street: Empire Ave
     - **Relationships**:
       - **University B**: COWORKER (TARGET: University B)
       - **Researcher C**: EMPLOYEE (TARGET: Researcher C)

   - **University B (EuroScience Institute)**:
     - **Industry**: Education
     - **Phone**: +33-144-555555
     - **Website**: www.euroscience.edu
     - **Email**: office@euroscience.edu
     - **Addresses**:
       - **Address 1**:
         - City: Paris
         - HouseNr: 77
         - Street: Science Boulevard
     - **Relationships**:
       - **Researcher D**: BOSS (TARGET: Researcher D)

   - **Researcher C (Dr. Julia Kim)**:
     - **Title**: Professor
     - **Phone**: +1-212-555-0147
     - **Email**: julia.kim@globaltech.edu
     - **Addresses**:
       - **Address 1**:
         - City: New York
         - HouseNr: 100
         - Street: Academic Way
     - **Relationships**:
       - **University A**: EMPLOYEE (TARGET: University A)
       - **University B**: COWORKER (TARGET: University B)

   - **Researcher D (Dr. Ahmed El Said)**:
     - **Title**: Research Fellow
     - **Phone**: +20-2-5555781
     - **Email**: ahmed.elsaid@euroscience.edu
     - **Addresses**:
       - **Address 1**:
         - City: Cairo
         - HouseNr: 200
         - Street: Nile Street

3. **Notes**
   - **Note for University A**:
     - **Author**: Dean Richard G.
     - **Time**: 2023-09-15
     - **Type**: MEETING
     - **Comment**: Annual collaboration review meeting scheduled.
   - **Note for Researcher C**:
     - **Author**: Prof. Lisa Wong
     - **Time**: 2023-08-20
     - **Type**: EMAIL
     - **Comment**: Follow-up on the joint paper submission highlights.

### Overconstraint Analysis

- **Violation**: The AddressBook model imposes a constraint on having at most one relationship for each contact, but this instance illustrates a multitude of roles for each contact, such as University A having multiple addresses due to its campuses in different cities and both universities having complex interactions with researchers via varied hierarchical and collaborative titles.

- **Insight**: This instance highlights potential overconstraints by showing a breakdown of multiple addresses and relationships, revealing gaps in capturing academic collaborations' dynamic nature. Updating the model to allow multiple address compositions and adaptable relationship statuses would better reflect the fluid connectivity inherent in such large-scale projects, enhancing its applicability for managing academic and cross-border teamwork effectively.

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

!new Company('GlobalTechUniversity')
!GlobalTechUniversity.name := 'GlobalTech University'
!GlobalTechUniversity.phone := '+1-617-555-6789'
!GlobalTechUniversity.website := 'www.globaltech.edu'
!GlobalTechUniversity.email := 'info@globaltech.edu'
!GlobalTechUniversity.industry := 'Education'

!new Address('GlobalTechAddress1')
!GlobalTechAddress1.city := 'Boston'
!GlobalTechAddress1.houseNr := '50'
!GlobalTechAddress1.street := 'College Road'
!insert (GlobalTechUniversity, GlobalTechAddress1) into ContactContainsAddress

!new Address('GlobalTechAddress2')
!GlobalTechAddress2.city := 'New York'
!GlobalTechAddress2.houseNr := '130'
!GlobalTechAddress2.street := 'Empire Ave'
!insert (GlobalTechUniversity, GlobalTechAddress2) into ContactContainsAddress

!new Company('EuroScienceInstitute')
!EuroScienceInstitute.name := 'EuroScience Institute'
!EuroScienceInstitute.phone := '+33-144-555555'
!EuroScienceInstitute.website := 'www.euroscience.edu'
!EuroScienceInstitute.email := 'office@euroscience.edu'
!EuroScienceInstitute.industry := 'Education'

!new Address('EuroScienceAddress')
!EuroScienceAddress.city := 'Paris'
!EuroScienceAddress.houseNr := '77'
!EuroScienceAddress.street := 'Science Boulevard'
!insert (EuroScienceInstitute, EuroScienceAddress) into ContactContainsAddress

!new Person('DrJuliaKim')
!DrJuliaKim.name := 'Dr. Julia Kim'
!DrJuliaKim.phone := '+1-212-555-0147'
!DrJuliaKim.email := 'julia.kim@globaltech.edu'
!DrJuliaKim.title := 'Professor'

!new Address('JuliaKimAddress')
!JuliaKimAddress.city := 'New York'
!JuliaKimAddress.houseNr := '100'
!JuliaKimAddress.street := 'Academic Way'
!insert (DrJuliaKim, JuliaKimAddress) into ContactContainsAddress

!new Person('DrAhmedElSaid')
!DrAhmedElSaid.name := 'Dr. Ahmed El Said'
!DrAhmedElSaid.phone := '+20-2-5555781'
!DrAhmedElSaid.email := 'ahmed.elsaid@euroscience.edu'
!DrAhmedElSaid.title := 'Research Fellow'

!new Address('AhmedElSaidAddress')
!AhmedElSaidAddress.city := 'Cairo'
!AhmedElSaidAddress.houseNr := '200'
!AhmedElSaidAddress.street := 'Nile Street'
!insert (DrAhmedElSaid, AhmedElSaidAddress) into ContactContainsAddress

!new Note('UniversityANote1')
!UniversityANote1.author := 'Dean Richard G.'
!UniversityANote1.time := Date('2023-09-15')
!UniversityANote1.type := #MEETING
!UniversityANote1.comment := 'Annual collaboration review meeting scheduled.'
!insert (GlobalTechUniversity, UniversityANote1) into ContactContainsNote

!new Note('ResearcherCNote1')
!ResearcherCNote1.author := 'Prof. Lisa Wong'
!ResearcherCNote1.time := Date('2023-08-20')
!ResearcherCNote1.type := #EMAIL
!ResearcherCNote1.comment := 'Follow-up on the joint paper submission highlights.'
!insert (DrJuliaKim, ResearcherCNote1) into ContactContainsNote

!new Relationship('GlobalTechToEuroScienceCoworker')
!GlobalTechToEuroScienceCoworker.type := #COWORKER
!insert (GlobalTechToEuroScienceCoworker, EuroScienceInstitute) into RelationshipToContact
!insert (GlobalTechUniversity, GlobalTechToEuroScienceCoworker) into ContactToRelationship

!new Relationship('GlobalTechToJuliaEmployee')
!GlobalTechToJuliaEmployee.type := #EMPLOYEE
!insert (GlobalTechToJuliaEmployee, DrJuliaKim) into RelationshipToContact
!insert (GlobalTechUniversity, GlobalTechToJuliaEmployee) into ContactToRelationship

!new Relationship('EuroScienceToAhmedBoss')
!EuroScienceToAhmedBoss.type := #BOSS
!insert (EuroScienceToAhmedBoss, DrAhmedElSaid) into RelationshipToContact
!insert (EuroScienceInstitute, EuroScienceToAhmedBoss) into ContactToRelationship

!new Relationship('JuliaToGlobalTechEmployee')
!JuliaToGlobalTechEmployee.type := #EMPLOYEE
!insert (JuliaToGlobalTechEmployee, GlobalTechUniversity) into RelationshipToContact
!insert (DrJuliaKim, JuliaToGlobalTechEmployee) into ContactToRelationship

!new Relationship('JuliaToEuroScienceCoworker')
!JuliaToEuroScienceCoworker.type := #COWORKER
!insert (JuliaToEuroScienceCoworker, EuroScienceInstitute) into RelationshipToContact
!insert (DrJuliaKim, JuliaToEuroScienceCoworker) into ContactToRelationship

!insert (ResearchCollaborationAddressBook, GlobalTechUniversity) into AddressBookMadeOfContact
!insert (ResearchCollaborationAddressBook, EuroScienceInstitute) into AddressBookMadeOfContact
!insert (ResearchCollaborationAddressBook, DrJuliaKim) into AddressBookMadeOfContact
!insert (ResearchCollaborationAddressBook, DrAhmedElSaid) into AddressBookMadeOfContact
</object_model>