Triple
T32062226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opus |
E818774
|
entity |
| Predicate | supportsBandwidthMode |
—
|
GENERATED |
| Object | narrowband |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBandwidthMode Context triple: [Opus, supportsBandwidthMode, narrowband]
-
A.
supportsBandwidths
chosen
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
B.
hasMaximumBandwidth
Indicates the maximum data transfer capacity that can be allocated, supported, or utilized in a given connection or system.
-
C.
bandwidthCharacteristic
Indicates the relationship specifying the bandwidth-related properties or constraints associated with a connection, link, or communication channel.
-
D.
hasGainBandwidthProductTypical
Indicates that an entity has a specified typical value for its gain–bandwidth product, describing the standard frequency–gain performance characteristic.
-
E.
usesChannelBandwidth
Indicates that one entity consumes or occupies a portion of the available bandwidth on a communication channel.
- F. None of above.
Provenance (1 batch)
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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:22 a.m.