Triple
T33203597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Type-C Alternate Mode architecture |
E849967
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | USB Type-C technology feature |
C58224
|
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: USB Type-C technology feature Context triple: [USB Type-C Alternate Mode architecture, instanceOf, USB Type-C technology feature]
-
A.
DisplayPort feature
A DisplayPort feature is a specific capability or enhancement of the DisplayPort interface standard that defines how audio, video, data, or control signals are transmitted, managed, or optimized between source and display devices.
-
B.
smartphone hardware feature
A smartphone hardware feature is a physical component or built-in device capability—such as a camera, fingerprint sensor, or NFC chip—that enables specific functions and interactions on a smartphone.
-
C.
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.
-
D.
USB 3.2 mode
USB 3.2 mode is an operational configuration of a USB connection that defines the data transfer rate, signaling method, and lane usage according to the USB 3.2 specification.
-
E.
Thunderbolt version
A Thunderbolt version represents a specific generation of the Thunderbolt hardware interface standard, defining its data transfer speeds, power delivery capabilities, connector type, and supported protocols.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:30 a.m.