Triple
T37051769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MST |
E917067
|
entity |
| Predicate | bandwidthLimitedBy |
P139996
|
FINISHED |
| Object | DisplayPort link rate and lane count |
—
|
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: DisplayPort link rate and lane count | Statement: [MST, bandwidthLimitedBy, DisplayPort link rate and lane count]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bandwidthLimitedBy Context triple: [MST, bandwidthLimitedBy, DisplayPort link rate and lane count]
-
A.
hasMaximumBandwidth
Indicates the maximum data transfer capacity that can be allocated, supported, or utilized in a given connection or system.
-
B.
bandwidthCharacteristic
chosen
Indicates the relationship specifying the bandwidth-related properties or constraints associated with a connection, link, or communication channel.
-
C.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
D.
lowerBandWidth
Indicates that one entity has a smaller or more limited bandwidth capacity than another.
-
E.
topBandWidth
Indicates the maximum data transfer capacity or throughput available at the upper limit of a connection, channel, or system.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.