Triple
T30786675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTP Payload Format for Uncompressed Video |
E783973
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | RTP payload format |
C57223
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: RTP payload format Context triple: [RTP Payload Format for Uncompressed Video, instanceOf, RTP payload format]
-
A.
RTP profile
An RTP profile defines a specific set of payload types, codecs, and protocol parameters that govern how real-time media is packetized, transmitted, and interpreted over the Real-time Transport Protocol.
-
B.
RTP receiver
An RTP receiver is a component that listens for and processes incoming Real-time Transport Protocol (RTP) packets, reconstructing media streams for playback or further handling.
-
C.
IP video transport standard
An IP video transport standard defines the protocols, formats, and procedures for reliably transmitting, routing, and synchronizing video and associated data over IP-based networks.
-
D.
MPEG-4 audio profile
An MPEG-4 audio profile is a standardized set of audio coding tools and constraints within the MPEG-4 framework that defines the capabilities, complexity, and interoperability of encoded audio streams.
-
E.
Audio Video Bridging protocol
Audio Video Bridging protocol is a set of IEEE Ethernet standards that provide time-synchronized, low-latency, and reliable transport of audio and video streams over local area networks.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:41 p.m.