Triple
T36663727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 1.0 |
E905201
|
entity |
| Predicate | dataRateFullSpeed |
P1376
|
FINISHED |
| Object | 12 Mbit/s |
—
|
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: 12 Mbit/s | Statement: [USB 1.0, dataRateFullSpeed, 12 Mbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataRateFullSpeed Context triple: [USB 1.0, dataRateFullSpeed, 12 Mbit/s]
-
A.
dataRateLowSpeed
Indicates that the data transmission rate is at a relatively low speed or bandwidth level.
-
B.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
C.
usbCDataTransferSpeed
Indicates the rate at which data can be transmitted over a USB-C connection between devices.
-
D.
passiveCableMaxSpeed
Indicates the maximum data transmission speed that can be supported when using a passive cable in the relationship.
-
E.
bandwidthCharacteristic
Indicates the relationship specifying the bandwidth-related properties or constraints associated with a connection, link, or communication channel.
- 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.