Triple
T17417180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.26x family of video coding standards |
E423517
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | video coding standard family |
C10956
|
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 coding standard family Context triple: [H.26x family of video coding standards, instanceOf, video coding standard family]
-
A.
video compression standard
chosen
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.
-
B.
video coding experts group
A video coding experts group is a specialized committee of professionals who develop, standardize, and optimize algorithms and formats for efficient digital video compression and transmission.
-
C.
video codec
A video codec is a software or hardware system that compresses and decompresses digital video data to enable efficient storage, transmission, and playback.
-
D.
digital broadcasting standard family
A digital broadcasting standard family is a group of related technical specifications that define how audio, video, and data are encoded, transmitted, and received over digital broadcast media to ensure interoperability and consistent quality across devices and services.
-
E.
MPEG-4 AVC
MPEG-4 AVC (also known as H.264) is a video compression standard that efficiently encodes digital video for storage and transmission while maintaining high visual quality at relatively low bitrates.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:46 a.m.