Triple
T9690958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ST 2022 |
E234532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | video over IP standard |
C8190
|
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: video over IP standard Context triple: [ST 2022, instanceOf, video over IP standard]
-
A.
IP video transport standard
chosen
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.
-
B.
video compression standard
A video compression standard is a defined set of algorithms and rules that specify how digital video is encoded, transmitted, stored, and decoded to reduce file size while maintaining acceptable visual quality.
-
C.
audio-over-IP interoperability standard
An audio-over-IP interoperability standard defines common protocols, formats, and control mechanisms that enable different networked audio devices and systems to exchange high-quality audio streams seamlessly over IP-based networks.
-
D.
broadcast television standard
A broadcast television standard is a defined set of technical specifications and protocols that govern how video and audio signals are encoded, transmitted, and received for over-the-air television broadcasting.
-
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.
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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:17 p.m.