Triple
T19451726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enhanced Audio Return Channel |
E486627
|
entity |
| Predicate | hasMaximumBandwidth |
P135964
|
FINISHED |
| Object | up to 37 Mbps |
—
|
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 37 Mbps | Statement: [Enhanced Audio Return Channel, hasMaximumBandwidth, up to 37 Mbps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumBandwidth Context triple: [Enhanced Audio Return Channel, hasMaximumBandwidth, up to 37 Mbps]
-
A.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
B.
usesChannelBandwidth
Indicates that one entity consumes or occupies a portion of the available bandwidth on a communication channel.
-
C.
maxTheoreticalBandwidthPerSlot
Indicates the maximum possible data transfer capacity that can be achieved per individual slot under ideal conditions.
-
D.
hasGainBandwidthProductTypical
Indicates that an entity has a specified typical value for its gain–bandwidth product, describing the standard frequency–gain performance characteristic.
-
E.
hasMaxMBsPerSecondExample
Indicates the maximum number of megabytes per second that an entity is allowed or able to handle, typically as an example throughput limit.
- F. None of above. chosen
Provenance (4 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63392aab08190aab09b7c356e5b10 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.