Triple

T28620130
Position Surface form Disambiguated ID Type / Status
Subject MPEG-DASH E724357 entity
Predicate supportsDRMIntegration P17307 FINISHED
Object yes LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: yes | Statement: [MPEG-DASH, supportsDRMIntegration, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsDRMIntegration
Context triple: [MPEG-DASH, supportsDRMIntegration, yes]
  • A. supportsDRMViaContainer
    Indicates that one entity enables or provides digital rights management (DRM) functionality through the use of a specific container format or packaging mechanism.
  • B. usesDRM chosen
    Indicates that one entity applies digital rights management (DRM) controls or technologies to another entity (such as content, software, or media).
  • C. hasDedicatedMediaKeys
    Indicates that an input device includes specific keys assigned to control media functions (such as play, pause, volume, or track navigation).
  • D. supportsMediaManagement
    Indicates that one entity provides functionality or assistance for organizing, handling, or controlling media content for another entity.
  • E. supportsStreamingIn
    Indicates that one entity provides or enables streaming functionality within a specified context, environment, or medium.
  • F. None of above.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69f01d822ac08190932de59ec2268ed2 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_6a0191d96dc88190ac0823e534f9d704 completed May 11, 2026, 8:22 a.m.
PD Predicate disambiguation batch_6a01908110448190a46442ffe4d15f5f completed May 11, 2026, 8:17 a.m.
Created at: April 28, 2026, 4:33 a.m.