Triple
T3800121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mini DisplayPort |
E91667
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital audio-video interface |
C14320
|
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 audio-video interface Context triple: [Mini DisplayPort, instanceOf, digital audio-video interface]
-
A.
digital media player
A digital media player is an electronic device or software application that stores, organizes, and plays digital audio, video, and image files from local or networked sources.
-
B.
HDMI feature
An HDMI feature is a specific capability or enhancement supported by an HDMI interface—such as audio return, Ethernet over HDMI, or high dynamic range—that defines how audio, video, and data are transmitted and experienced between connected devices.
-
C.
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.
-
D.
virtual multichannel video programming distributor
A virtual multichannel video programming distributor is an online service that delivers multiple live television channels and related video content over the internet without owning traditional physical transmission infrastructure like cable or satellite systems.
-
E.
digital input signal
A digital input signal is a discrete electrical or logical signal, typically represented by two states (such as HIGH/LOW or 1/0), used to convey binary information into a digital system or device.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.