| 1 Definition | 2 Functional Requirements | 3 Syntax |
| 4 Semantics | 5 Conformance Testing | 6 Performance Assessment |
Definition
The digital representation of predicates and their associated semantic roles – covering participants, contextual parameters, and relationships – designed to enable consistent interpretation of events and states, and to support precise, extensible binding of roles (according to ISO 24617-4:2014).
Functional Requirements
MUST Requirements
- Predicate Core — MUST represent predicates with type, sense/lemma, aspect, polarity, modality, and voice where applicable.
- Role Inventory — MUST provide a canonical inventory of semantic roles (Agent, Patient, Experiencer, Instrument, Source, Goal, Location, Time) with definitions and constraints.
- Role Binding — MUST support explicit binding of roles to arguments (entities, values, events, times) with cardinality and role-specific constraints.
- Argument Typing — MUST support typing of arguments (Entity, Event, State, Time, Value, Proposition) and sub-typing via controlled vocabularies.
- Argument Realisation — MUST distinguish abstract role assignment from surface realisation (syntactic position, expression anchor, implicit/explicit).
- Compositionality — MUST support multi-predicate structures and scoped role inheritance/overrides.
- TER Linkage — MUST provide scope references to TER relation IDs for temporal context instead of encoding temporal logic internally.
- TEE Integration — MUST allow linking predicates and roles to TEE events and expressions for multimodal anchoring.
- Normalisation — MUST normalise predicate and role identifiers to stable namespaces (URIs/IRIs) with language-independent base IDs.
- Identity and Referencing — MUST ensure stable identifiers for Predicate, Role, and Role Binding entities; support cross-reference and uniqueness.
- Constraints — MUST encode role selection preferences and constraints declaratively.
- Polymorphism & Alternations — MUST model diathesis alternations with consistent role mapping across realisations.
- Scope & Negation — MUST represent scope relations for modality, negation, quantification, and intentional contexts.
- Cross-Ontology Alignment — MUST provide mapping hooks to external resources without requiring any single ontology.
- Multilingual Support — MUST support multilingual labels and cross-lingual predicate sense alignment.
- Trace — MUST record provenance metadata for predicates, roles, bindings, and changes.
- Extensibility — MUST allow controlled extension points without breaking conformance.
SHOULD Requirements
- Profiles — SHOULD support domain-specific profiles with additional role sets and constraints.
- Quality Measures — SHOULD provide optional confidence scores, quality flags, and validation reports.
- Queryability — SHOULD facilitate efficient querying by predicate type, role, argument type, language, time window, modality, and provenance.
- Role Hierarchies — SHOULD support role taxonomies and inheritance for generalisation and reasoning.
- Defaulting & Implicit Roles — SHOULD represent conventional defaults and implicit roles with explicit markers.
- Event Integration — SHOULD provide bridging structures to TEE and TER for unified reasoning about events and roles.
Syntax
https://schemas.mpai.community/MMC/V2.5/data/PredicateRoleMapping.json
Semantics
| Label | Description |
| Header | PRM Schema Header (schema title and header context) |
| ├─ Standard‑PRM | Literal prefix identifying PRM schema (e.g., “MMC‑PRM‑V” embedded in Header pattern) |
| ├─ Version | Major version – 1 or 2 digits (part of Header pattern) |
| ├─ Dot‑separator | The character “.” separating version components (part of Header pattern) |
| ├─ Subversion | Minor version – 1 or 2 digits (part of Header pattern) |
| trace | Provenance metadata for the PRM instance |
| ├─ origin | Source system or module that produced the PRM instance (string) |
| ├─ timestamp | Creation/modification time (RFC 3339 date‑time) |
| predicate | Predicate occurrence object describing the predicate instance |
| ├─ predicateId | Stable identifier of the predicate occurrence in the annotation layer (string) |
| ├─ lemma | Canonical form (lemma) of the predicate (string) |
| ├─ pos | Part‑of‑speech of the predicate (e.g., verb, noun, adjective) (string) |
| ├─ sense | Lexical sense or frame identifier if available (string or null) |
| ├─ provenance | Optional link to source spans (text/audio/video) |
| predicate.provenance | Anchors locating the predicate in source media |
| ├─ textSpan | [start, end) character offsets (array of integers) |
| ├─ timeSpan | [start, end) seconds in media (array of numbers) |
| arguments[] | Array of role arguments (minItems=1) |
| ├─ role | Semantic role label from RoleVocabulary (ISO 24617‑4 starter set) |
| ├─ filler | Argument value: string, number, or object with ref/text |
| ├─ confidence | Optional confidence score (0..1) |
| ├─ provenance | Optional anchors locating the argument in source media |
| arguments[].filler | Concrete filler variants |
| ├─ string | Literal string value for the argument |
| ├─ number | Numeric value for the argument |
| ├─ object | Structured filler with ref/text |
| arguments[].filler.object | Structured filler fields |
| ├─ ref | ID reference to an entity/object in the world model (string) |
| ├─ text | Surface form if no ID available (string) |
| arguments[].provenance | Anchors locating the argument in source media |
| ├─ textSpan | [start, end) character offsets (array of integers) |
| ├─ timeSpan | [start, end) seconds in media (array of numbers) |
| metadata | Optional metadata for the PRM instance (additionalProperties=true) |
| ├─ language | Language tag or identifier (string) |
| ├─ schemaVersion | Schema version string (string) |
| RoleVocabulary | Enumerated semantic roles (starter set aligned with ISO 24617‑4) |
| ├─ Agent | Actor initiating or controlling the event |
| ├─ Patient | Entity undergoing the action/effect |
| ├─ Theme | Entity moved, located, or affected |
| ├─ Experiencer | Entity experiencing a state or stimulus |
| ├─ Stimulus | Cause that elicits an experience |
| ├─ Instrument | Means used to perform an action |
| ├─ Beneficiary | Entity benefiting from an event |
| ├─ Recipient | Entity receiving something |
| ├─ Source | Origin or starting point |
| ├─ Goal | Target or endpoint |
| ├─ Location | Place where event occurs |
| ├─ Path | Route or trajectory |
| ├─ Manner | Way in which action is performed |
| ├─ Cause | Reason or causal factor |
| ├─ Purpose | Intended outcome |
| ├─ Comitative | Entity accompanying another |
| ├─ Temporal | Time or time expression |
| ├─ Duration | Temporal length |
5 Conformance Testing
A Data instance Conforms with MPAI-MMC Belief (MMC-EBL) if:
- Its JSON Object validates against its JSON Schema.
- Any included JSON Object validates against its JSON Schema.
- All Data in the JSON Object:
- Have the specified Data Types.
- Conform with the Qualifiers signaled in their JSON Schemas.
