Triple
T25933227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolt 4 |
E653483
|
entity |
| Predicate | requiresMinimumPCIeBandwidth |
P79916
|
FINISHED |
| Object | 32 Gbit/s PCIe (PCIe 3.0 x4) |
—
|
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: 32 Gbit/s PCIe (PCIe 3.0 x4) | Statement: [Thunderbolt 4, requiresMinimumPCIeBandwidth, 32 Gbit/s PCIe (PCIe 3.0 x4)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresMinimumPCIeBandwidth Context triple: [Thunderbolt 4, requiresMinimumPCIeBandwidth, 32 Gbit/s PCIe (PCIe 3.0 x4)]
-
A.
supportsPCIeVersion
Indicates that one entity is compatible with or able to operate using a specified version of the PCI Express (PCIe) standard.
-
B.
suppliedGPUFor
Indicates that one entity provided or furnished a GPU to another entity for its use or operation.
-
C.
hasMiniPCI
Indicates that one entity is equipped with or includes a Mini PCI (Peripheral Component Interconnect) interface or slot.
-
D.
supportsGPUType
Indicates that one entity is compatible with, or capable of operating using, a specified type of GPU.
-
E.
requiresSpeed
chosen
Indicates that an entity needs to be performed, operated, or handled at or above a certain speed in order to be valid or effective.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 22, 2026, 8:37 a.m.