Triple
T26242278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lattice ECP5 |
E656346
|
entity |
| Predicate | serdesSpeed |
P139996
|
FINISHED |
| Object | up to 5 Gbps (ECP5-5G variants) |
—
|
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: up to 5 Gbps (ECP5-5G variants) | Statement: [Lattice ECP5, serdesSpeed, up to 5 Gbps (ECP5-5G variants)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serdesSpeed Context triple: [Lattice ECP5, serdesSpeed, up to 5 Gbps (ECP5-5G variants)]
-
A.
supportsBusSpeed
Indicates that one entity is capable of operating at, or is compatible with, a specified bus communication speed of another entity.
-
B.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
-
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
chosen
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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60d8f7f9c8190bb8cb8f8ac4c0ca5 |
completed | May 2, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:04 p.m.