Triple
T36663780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 3.0 |
E905202
|
entity |
| Predicate | marketingNameDataRate |
P1376
|
FINISHED |
| Object | SuperSpeed 5 Gbps |
—
|
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: SuperSpeed 5 Gbps | Statement: [USB 3.0, marketingNameDataRate, SuperSpeed 5 Gbps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketingNameDataRate Context triple: [USB 3.0, marketingNameDataRate, SuperSpeed 5 Gbps]
-
A.
marketingNameOf
Indicates that one entity is the marketing or brand name used to promote or refer to another entity.
-
B.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
C.
marketingNameRegion
Indicates the association between a marketing name and the specific geographic region or market where that name is used or applicable.
-
D.
symbolRates
Indicates a quantitative rate or value associated with a given symbol in relation to another reference (such as time, currency, or unit).
-
E.
marketingNameChange
Indicates that an entity’s marketing or brand name has been changed from one name to another.
- 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_69f7c77ef4108190aa83a9f595e34905 |
completed | May 3, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.