Triple
T11305700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DisplayPort Multi-Stream Transport |
E267707
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital display interface technology |
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 display interface technology Context triple: [DisplayPort Multi-Stream Transport, instanceOf, digital display interface technology]
-
A.
display technology
Display technology encompasses the various electronic methods and devices used to visually present information, images, and video to users, such as LCD, OLED, and projection systems.
-
B.
digital audio-video interface
chosen
A digital audio-video interface is a standardized connection system that transmits high-quality digital audio and video signals between electronic devices.
-
C.
aperture grille cathode-ray tube display technology
Aperture grille cathode-ray tube display technology uses vertical tensioned wires instead of a traditional shadow mask to allow more electron beam energy to reach the phosphors, producing brighter and sharper images with improved color accuracy.
-
D.
digital instrument cluster
A digital instrument cluster is an electronic display system in a vehicle that replaces traditional analog gauges to present real-time driving information such as speed, RPM, fuel level, and warnings in a customizable, often graphical format.
-
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.
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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:32 p.m.