{"id":9098,"date":"2026-08-25T01:07:05","date_gmt":"2026-08-25T01:07:05","guid":{"rendered":"https:\/\/metaphaze.com\/gazettebuilder\/?page_id=9098"},"modified":"2026-08-25T01:07:05","modified_gmt":"2026-08-25T01:07:05","slug":"documentation-semantic-relationships","status":"publish","type":"page","link":"https:\/\/metaphaze.com\/gazettebuilder\/documentation-semantic-relationships\/","title":{"rendered":"Documentation: Semantic Relationships"},"content":{"rendered":"\n

Semantic Relationships connect one GazetteBuilder Entry to another using the controlled vocabulary defined under:<\/p>\n\n\n\n

GazetteBuilder \u2192 Relationship Definitions<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

They are entered on the source Entry in the Relationships<\/strong> field and use the format:<\/p>\n\n\n\n

Relationship Name: Target Entry<\/pre>\n\n\n\n
Enter one relationship per line.<\/p>\n\n\n\n
For example:<\/p>\n\n\n\n
Located in: Syrtis Major
In District: Residency
On Street: Bedford Road<\/pre>\n\n\n\n
Relationship Name<\/h2>\n\n\n\n
The text before the colon must match the Name<\/strong> of an existing Relationship Definition.<\/p>\n\n\n\n
For example, if the Relationship Definition uses:<\/p>\n\n\n\n
Name: Located in<\/pre>\n\n\n\n
then the Entry should use:<\/p>\n\n\n\n
Located in: Syrtis Major<\/pre>\n\n\n\n
Relationship names are controlled vocabulary. Do not substitute alternate wording unless a separate Relationship Definition exists for that wording.<\/p>\n\n\n\n
Target Entry<\/h2>\n\n\n\n
The text after the colon identifies the Entry the relationship points to.<\/p>\n\n\n\n
For example:<\/p>\n\n\n\n
Located in: Syrtis Major<\/pre>\n\n\n\n
means that the current Entry is related to the Entry named Syrtis Major<\/strong> through the Located in<\/strong> relationship.<\/p>\n\n\n\n
The target must also be compatible with the Target Type configured in the Relationship Definition.<\/p>\n\n\n\n
Source and Target Types<\/h2>\n\n\n\n
Relationship Definitions specify which Entry Types may appear on each side of the relationship.<\/p>\n\n\n\n
For example:<\/p>\n\n\n\n
Relationship: Located in
Source Type: Location
Target Type: Location<\/pre>\n\n\n\n
allows a Location Entry such as the Dorchester Hotel to declare:<\/p>\n\n\n\n
Located in: Syrtis Major<\/pre>\n\n\n\n
If the source or target Entry Type does not match the definition, the relationship does not satisfy that Relationship Definition.<\/p>\n\n\n\n
Entering Relationships on an Entry<\/h2>\n\n\n\n
Open or edit an Entry and locate the Relationships<\/strong> field in the GazetteBuilder Entry Details section.<\/p>\n\n\n\n
Enter each declaration on its own line:<\/p>\n\n\n\n
Located in: Syrtis Major
In District: Residency
On Street: Bedford Road<\/pre>\n\n\n\n
The Relationship Name comes from the Relationship Definition. The Target Entry is the Entry being referenced.<\/p>\n\n\n\n
Unlike semantic references in the article text, relationships are entered in this dedicated metadata field rather than inside [[double brackets]]<\/code>.<\/p>\n\n\n\n
Forward Presentation<\/h2>\n\n\n\n
A resolved relationship can be presented on the source Entry as part of its relationship or reference information.<\/p>\n\n\n\n
For example, the Dorchester Hotel might declare:<\/p>\n\n\n\n
Located in: Syrtis Major
In District: Hotel District<\/pre>\n\n\n\n
GazetteBuilder can then present those relationships on the Dorchester Hotel Entry with links to the resolved targets.<\/p>\n\n\n\n
The relationship is stored once on the source Entry.<\/p>\n\n\n\n
Reverse Presentation<\/h2>\n\n\n\n
The same relationship can also be used in the opposite direction.<\/p>\n\n\n\n
Each Relationship Definition includes an Inverse Label<\/strong>. GazetteBuilder can use that label to build a reverse listing on the Target Entry.<\/p>\n\n\n\n
For example, the definition:<\/p>\n\n\n\n
Name: Located in
Inverse Label: Locations<\/pre>\n\n\n\n
allows Entries such as:<\/p>\n\n\n\n
Dorchester Hotel \u2192 Located in \u2192 Syrtis Major
Government House \u2192 Located in \u2192 Syrtis Major
Residency Park \u2192 Located in \u2192 Syrtis Major<\/pre>\n\n\n\n
to contribute automatically to a section on the Syrtis Major Entry such as:<\/p>\n\n\n\n
Locations<\/strong><\/p>\n\n\n\n
    \n
  • Dorchester Hotel<\/li>\n\n\n\n
  • Government House<\/li>\n\n\n\n
  • Residency Park<\/li>\n<\/ul>\n\n\n\n
    The Syrtis Major Entry does not need to maintain that list manually.<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    Different Relationships Can Produce Different Reverse Sections<\/h2>\n\n\n\n
    The Inverse Label belongs to the Relationship Definition, so each kind of relationship can use wording appropriate to its meaning.<\/p>\n\n\n\n
    For example:<\/p>\n\n\n\n
    Name: In District
    Inverse Label: Locations in this District<\/pre>\n\n\n\n
    can generate:<\/p>\n\n\n\n
    Locations in this District<\/strong><\/p>\n\n\n\n
    while:<\/p>\n\n\n\n
    Name: Located in
    Inverse Label: Locations<\/pre>\n\n\n\n
    can generate:<\/p>\n\n\n\n
    Locations<\/strong><\/p>\n\n\n\n
    This lets Gazette Builder organize related Entries according to the meaning of the relationship rather than simply collecting every backlink into one list.<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    Relationship Definitions Control Valid Usage<\/h2>\n\n\n\n
    Before entering a relationship, check the relevant Relationship Definition.<\/p>\n\n\n\n
    It determines:<\/p>\n\n\n\n
      \n
    • the canonical Relationship Name;<\/li>\n\n\n\n
    • the permitted Source Entry Type;<\/li>\n\n\n\n
    • the permitted Target Entry Type;<\/li>\n\n\n\n
    • the Inverse Label used for reverse presentation.<\/li>\n<\/ul>\n\n\n\n
      For example:<\/p>\n\n\n\n
      ID: in_district
      Name: In District
      Inverse Label: Locations in this District
      Source Type: Location
      Target Type: Location<\/pre>\n\n\n\n
      supports a declaration such as:<\/p>\n\n\n\n
      In District: Residency<\/pre>\n\n\n\n
      on a Location Entry when Residency<\/strong> is also a Location Entry.<\/p>\n\n\n\n
      Relationships and Semantic References Are Different<\/h2>\n\n\n\n
      Both features connect Entries, but they serve different purposes.<\/p>\n\n\n\n
      A semantic reference appears in normal article content:<\/p>\n\n\n\n
      [[Syrtis Major]]<\/pre>\n\n\n\n
      It means that the article refers to the Syrtis Major Entry.<\/p>\n\n\n\n
      A semantic relationship appears in the Relationships field:<\/p>\n\n\n\n
      Located in: Syrtis Major<\/pre>\n\n\n\n
      It tells Gazette Builder what the connection between the two Entries means.<\/p>\n\n\n\n
      An Entry may use both.<\/p>\n\n\n\n
      For example, the prose might say:<\/p>\n\n\n\n
      The hotel stands near the colonial center of [[Syrtis Major]].<\/pre>\n\n\n\n
      while its Relationships field contains:<\/p>\n\n\n\n
      Located in: Syrtis Major<\/pre>\n\n\n\n
      The first provides an in-text semantic reference. The second provides structured relationship information that GazetteBuilder can use for forward and reverse presentation.<\/p>\n\n\n\n
      Editing Relationship Definitions<\/h2>\n\n\n\n
      Because Entry relationships rely on the canonical Name defined under Relationship Definitions<\/strong>, changes to an existing definition can affect relationships already entered on Entries.<\/p>\n\n\n\n
      When changing or deleting a Relationship Definition, review the Entries that use it and update their relationship declarations where necessary.<\/p>\n\n\n\n
      Typical Workflow<\/h2>\n\n\n\n
      To add a Semantic Relationship:<\/p>\n\n\n\n
        \n
      1. Confirm that the required Relationship Definition exists.<\/li>\n\n\n\n
      2. Confirm that the source Entry uses an allowed Source Type.<\/li>\n\n\n\n
      3. Confirm that the target Entry uses an allowed Target Type.<\/li>\n\n\n\n
      4. Open the source Entry.<\/li>\n\n\n\n
      5. Add a line to the Relationships<\/strong> field using:<\/li>\n<\/ol>\n\n\n\n
        Relationship Name: Target Entry<\/pre>\n\n\n\n
          \n
        1. Save the Entry.<\/li>\n\n\n\n
        2. View the Entry to confirm the forward relationship.<\/li>\n\n\n\n
        3. View the Target Entry to confirm the expected inverse listing where applicable.<\/li>\n<\/ol>\n\n\n\n
          Semantic Relationships therefore let Gazette Builder use one structured declaration in two useful ways: to describe the connection on the source Entry and to organize related Entries automatically on the target Entry.<\/p>\n","protected":false},"excerpt":{"rendered":"
          Semantic Relationships connect one GazetteBuilder Entry to another using the controlled vocabulary defined under: GazetteBuilder \u2192 Relationship Definitions They are entered on the source Entry in the Relationships field and use the format: Relationship Name: Target Entry Enter one relationship per line. For example: Located in: Syrtis MajorIn District: ResidencyOn Street: Bedford Road Relationship Name […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-9098","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/pages\/9098","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/comments?post=9098"}],"version-history":[{"count":1,"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/pages\/9098\/revisions"}],"predecessor-version":[{"id":9102,"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/pages\/9098\/revisions\/9102"}],"wp:attachment":[{"href":"https:\/\/metaphaze.com\/gazettebuilder\/wp-json\/wp\/v2\/media?parent=9098"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}