Skip to content

Main content

Ontology Edge Inverse Label

Reverse one ontology edge using an explicitly supplied inverse predicate without inferring ontology semantics.

Loading tool…

Description

Construct an inverse ontology-edge record using a supplied inverse predicate.

Information records distinguish identifiers, controlled vocabularies, language fallbacks, assertion times and valid times. A supplied inverse predicate differs from an inferred semantic relation. Text offsets require an explicit code-point or code-unit basis, and a metadata count check does not validate field content or an entire schema.

Construct an inverse ontology-edge record using a supplied inverse predicate.

When to use this tool

Use Ontology Edge Inverse Label when you already have subjectId, predicateId, objectId, inversePredicateId and need to construct an inverse ontology-edge record using a supplied inverse predicate.

How to use the tool and how it works

  1. Enter subjectId, predicateId, objectId, inversePredicateId. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read inverseSubject, inversePredicate, inverseObject. Use the output convention below.

Require subject/predicate/object/inversePredicate IDs nonempty; output subject=old object, predicate=supplied inverse and object=old subject.1

Input fieldMeaning and unitsAccepted input
subjectIdSubject IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
predicateIdRequired source predicate label; not used to infer the inverse predicate.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
objectIdObject IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
inversePredicateIdSupplied output predicate; the subject and object are swapped without ontology reasoning.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
inverseSubjectInverse SubjectRequired. Text; maximum UTF-16 length 8192.
inversePredicateInverse PredicateRequired. Text; maximum UTF-16 length 8192.
inverseObjectInverse ObjectRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "subjectId": "A",
    "predicateId": "parentOf",
    "objectId": "B",
    "inversePredicateId": "childOf"
  },
  "output": {
    "inverseSubject": "B",
    "inversePredicate": "childOf",
    "inverseObject": "A"
  }
}

Limitations and assumptions

  • The original predicate is required but no inverse mapping is inferred or verified; this does not prove the new assertion or alter a graph.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use the actual record, vocabulary authority and complete metadata schema for semantic or conformance questions. Apply the identifier scheme's real comparison rules and the intended language/offset policy rather than inferring them from a local string operation.

References

  1. Calculation and input contract: information-science/ontology-edge-inverse-label — tool.io

Similar or alternative tools