Triple
T29390418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UHS-I |
E745355
|
entity |
| Predicate | dataTransferRateComparedTo |
P141975
|
FINISHED |
| Object | higher than standard SD |
—
|
LITERAL FINISHED |
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: higher than standard SD | Statement: [UHS-I, dataTransferRateComparedTo, higher than standard SD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTransferRateComparedTo Context triple: [UHS-I, dataTransferRateComparedTo, higher than standard SD]
-
A.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
B.
usbCDataTransferSpeed
Indicates the rate at which data can be transmitted over a USB-C connection between devices.
-
C.
bandwidthCharacteristic
Indicates the relationship specifying the bandwidth-related properties or constraints associated with a connection, link, or communication channel.
-
D.
hasHigherThroughputThan
chosen
Indicates that one entity can process or transmit a greater volume of work, data, or operations per unit time than another entity.
-
E.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d648488190b7d3060432eb0eeb |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 2:41 p.m.