Triple
T28470836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-1 |
E720431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital transmission format |
C13903
|
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: digital transmission format Context triple: [STS-1, instanceOf, digital transmission format]
-
A.
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.
-
B.
digital audio codec
A digital audio codec is a system or algorithm that encodes and compresses audio signals into a digital format for storage or transmission and decodes them back into audio for playback.
-
C.
high-definition video format
A high-definition video format is a digital video standard that delivers significantly higher resolution, clarity, and detail than standard-definition formats, typically including 720p, 1080p, or higher resolutions.
-
D.
digital line code
chosen
A digital line code is a method of representing digital data as a specific pattern of voltage, current, or light level changes over a transmission medium to enable reliable communication between devices.
-
E.
streaming media format
A streaming media format is a standardized method for encoding, packaging, and transmitting audio and/or video data over a network so it can be played in real time as it is received rather than after full download.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:48 a.m.