Triple
T11115344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 2.0 |
E262871
|
entity |
| Predicate | highSpeedRate |
P1376
|
FINISHED |
| Object | 480 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: 480 Mbit/s | Statement: [USB 2.0, highSpeedRate, 480 Mbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highSpeedRate Context triple: [USB 2.0, highSpeedRate, 480 Mbit/s]
-
A.
increasedRateOn
Indicates that one entity has raised the rate, fee, or charge applied to another entity.
-
B.
openedAsHighSpeed
Indicates that something was inaugurated or began operation specifically as a high-speed service or facility.
-
C.
primaryHighSpeedOperator
Indicates that an entity serves as the main operator responsible for providing high-speed service or functionality to another entity.
-
D.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
E.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa7254c8190abce35696ad2be03 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.