Triple
T36663788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 3.0 |
E905202
|
entity |
| Predicate | supportsFullDuplexDataTransfer |
—
|
GENERATED |
| Object | true |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFullDuplexDataTransfer Context triple: [USB 3.0, supportsFullDuplexDataTransfer, true]
-
A.
laterSupportedDuplexMode
Indicates that one entity provided support for duplex mode at a later time than another entity.
-
B.
duplexMode
chosen
Indicates whether a communication link or device operates in half-duplex or full-duplex mode, defining if data can flow in one or both directions simultaneously.
-
C.
usesDuplexMethod
Indicates that one entity employs a duplex method, meaning a two-way or bidirectional technique or process, in relation to another entity or context.
-
D.
supportsMultipleStreams
Indicates that the subject is capable of handling or maintaining more than one data or communication stream at the same time.
-
E.
supportsDataExchange
Indicates that one entity enables or facilitates the transfer or sharing of data with another entity.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.