Triple
T9191652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AES67 |
E220603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | audio-over-IP interoperability standard |
C25789
|
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: audio-over-IP interoperability standard Context triple: [AES67, instanceOf, audio-over-IP interoperability standard]
-
A.
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.
-
B.
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.
-
C.
multichannel audio format
A multichannel audio format is a digital or analog audio configuration that uses more than two discrete channels to reproduce sound from multiple directions, enhancing spatial realism and immersion.
-
D.
media gateway control protocol
A media gateway control protocol is a signaling protocol that enables a media gateway controller to manage media gateways for the setup, modification, and teardown of multimedia sessions across packet and circuit-switched networks.
-
E.
wideband speech codec
A wideband speech codec is a digital encoding and decoding system that compresses and reconstructs speech signals over an extended frequency range (typically 50 Hz–7 kHz or higher) to improve clarity and naturalness compared to narrowband codecs.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:24 p.m.