Triple
T425226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB4 |
E8192
|
entity |
| Predicate | maxDataRate |
P1376
|
FINISHED |
| Object | 40 Gbit/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: 40 Gbit/s | Statement: [USB4, maxDataRate, 40 Gbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxDataRate Context triple: [USB4, maxDataRate, 40 Gbit/s]
-
A.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
B.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
C.
maxCurrent
Indicates the maximum electric current that is allowed to flow through or be drawn by an entity under specified conditions.
-
D.
maximumPayload
Indicates the greatest amount of load or capacity that an entity is designed or allowed to carry, handle, or support.
-
E.
maximumService
Indicates that an entity provides the highest allowable or achievable level of service within a given context or system.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.