Triple
T36663815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 3.0 |
E905202
|
entity |
| Predicate | improvesDataTransferRateComparedTo |
P141975
|
FINISHED |
| Object | USB 2.0 |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: USB 2.0 | Statement: [USB 3.0, improvesDataTransferRateComparedTo, USB 2.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: improvesDataTransferRateComparedTo Context triple: [USB 3.0, improvesDataTransferRateComparedTo, USB 2.0]
-
A.
hasHigherThroughputThan
chosen
Indicates that one entity can process or transmit a greater volume of work, data, or operations per unit time than another entity.
-
B.
advantageOverSATA
Indicates that one entity has a performance or functional benefit when compared to SATA.
-
C.
usbCDataTransferSpeed
Indicates the rate at which data can be transmitted over a USB-C connection between devices.
-
D.
bandwidthEfficiency
Indicates how effectively available bandwidth is utilized to transmit data relative to capacity or resource usage.
-
E.
supportsBusSpeed
Indicates that one entity is capable of operating at, or is compatible with, a specified bus communication speed of another entity.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.