Triple
T36663755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 1.0 |
E905201
|
entity |
| Predicate | supportsInterruptTransfers |
—
|
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: supportsInterruptTransfers Context triple: [USB 1.0, supportsInterruptTransfers, true]
-
A.
supportsInterrupt
Indicates that one entity is capable of handling or accommodating an interruption initiated by another entity.
-
B.
supportsInterruptMasking
Indicates that one entity provides the capability to temporarily disable or mask interrupts for another entity or operation.
-
C.
supportsInterruptPriorities
Indicates that one entity provides or is compatible with a mechanism for assigning and handling different priority levels for interrupts associated with another entity.
-
D.
supportsTransactions
Indicates that one entity provides the capability for another entity to perform or manage transactions reliably.
-
E.
supportsRasterInterrupts
Indicates that the system or component is capable of handling raster interrupts during display or rendering operations.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.