Triple
T11305619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCI-X |
E267705
|
entity |
| Predicate | maxTheoreticalBandwidthPerSlot |
P98411
|
FINISHED |
| Object | 1064 MB/s |
—
|
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: 1064 MB/s | Statement: [PCI-X, maxTheoreticalBandwidthPerSlot, 1064 MB/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxTheoreticalBandwidthPerSlot Context triple: [PCI-X, maxTheoreticalBandwidthPerSlot, 1064 MB/s]
-
A.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
B.
hasGainBandwidthProductTypical
Indicates that an entity has a specified typical value for its gain–bandwidth product, describing the standard frequency–gain performance characteristic.
-
C.
maxSpatialStreams
Indicates the maximum number of simultaneous spatial data streams that can be used or supported in a communication or processing context.
-
D.
maxSlotsPerSystem
Indicates the maximum number of slots that are allowed or can be allocated within a single system.
-
E.
usesChannelBandwidth
Indicates that one entity consumes or occupies a portion of the available bandwidth on a communication channel.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a7255c81909675fe9ad6d71934 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.