Triple
T32377479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVR-MS |
E827328
|
entity |
| Predicate | supportsTimeShifting |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTimeShifting Context triple: [DVR-MS, supportsTimeShifting, yes]
-
A.
supportsTimeStretch
Indicates that one entity provides the capability to alter the duration of another entity (such as audio or video) without changing its pitch.
-
B.
timeShiftService
Indicates that a service is provided with a shifted or delayed time relative to its original or real-time schedule.
-
C.
supportsTimecodes
Indicates that one entity can handle, interpret, or work with timecode information associated with another entity or data stream.
-
D.
supportsTimescale
Indicates that one entity is capable of operating with, accommodating, or being compatible with a specified timescale or range of temporal resolutions.
-
E.
timeShiftProperty
Indicates a relationship where one property value is derived from another by applying a temporal shift (e.g., offsetting it to an earlier or later point in time).
- F. None of above. chosen
Provenance (1 batch)
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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:51 a.m.