Triple
T29502600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SFF-8088 |
E748414
|
entity |
| Predicate | aggregateBandwidth |
P132852
|
FINISHED |
| Object | up to 24 Gbit/s for 4 lanes at 6 Gbit/s each |
—
|
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 24 Gbit/s for 4 lanes at 6 Gbit/s each | Statement: [SFF-8088, aggregateBandwidth, up to 24 Gbit/s for 4 lanes at 6 Gbit/s each]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggregateBandwidth Context triple: [SFF-8088, aggregateBandwidth, up to 24 Gbit/s for 4 lanes at 6 Gbit/s each]
-
A.
networkBand
Indicates the specific frequency band or range within a network over which communication or data transmission occurs.
-
B.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
C.
aggregateRate
chosen
Indicates a combined or overall rate derived from multiple individual rates or components.
-
D.
hasMaximumBandwidth
Indicates the maximum data transfer capacity that can be allocated, supported, or utilized in a given connection or system.
-
E.
bandwidthClass
Indicates the classification of a connection or resource based on its available or allocated bandwidth capacity.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c33d4bc81908ab72b03c1d747c6 |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 4:25 p.m.