Triple
T9026995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGP |
E216071
|
entity |
| Predicate | maxTheoreticalBandwidth |
P45736
|
FINISHED |
| Object | 266 MB/s at 1x |
—
|
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: 266 MB/s at 1x | Statement: [AGP, maxTheoreticalBandwidth, 266 MB/s at 1x]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxTheoreticalBandwidth Context triple: [AGP, maxTheoreticalBandwidth, 266 MB/s at 1x]
-
A.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
B.
maximumBitrate
chosen
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
C.
maxSpatialStreams
Indicates the maximum number of simultaneous spatial data streams that can be used or supported in a communication or processing context.
-
D.
hasGainBandwidthProductTypical
Indicates that an entity has a specified typical value for its gain–bandwidth product, describing the standard frequency–gain performance characteristic.
-
E.
maxDataTransferMode
Indicates the data transfer mode in which the maximum possible data throughput is achieved between entities.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7eb5b881908ace0c3327f06161 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.