Triple
T29390455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SD Express |
E745356
|
entity |
| Predicate | providesMaxThroughput |
P135964
|
FINISHED |
| Object | up to 985 MB/s with PCIe 3.0 x1 |
—
|
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 985 MB/s with PCIe 3.0 x1 | Statement: [SD Express, providesMaxThroughput, up to 985 MB/s with PCIe 3.0 x1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesMaxThroughput Context triple: [SD Express, providesMaxThroughput, up to 985 MB/s with PCIe 3.0 x1]
-
A.
hasMaximumBandwidth
chosen
Indicates the maximum data transfer capacity that can be allocated, supported, or utilized in a given connection or system.
-
B.
hasHigherThroughputThan
Indicates that one entity can process or transmit a greater volume of work, data, or operations per unit time than another entity.
-
C.
requiresMinimumDataThroughputPerPort
Indicates that a certain action or configuration is contingent on each port supporting at least a specified minimum data throughput.
-
D.
hasLowerThroughputThan
Indicates that one entity’s throughput is less than that of another entity.
-
E.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 28, 2026, 2:42 p.m.