Triple
T31632332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA GeForce RTX 4090 |
E807201
|
entity |
| Predicate | pcieInterface |
P41289
|
FINISHED |
| Object | PCIe 4.0 x16 |
—
|
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: PCIe 4.0 x16 | Statement: [NVIDIA GeForce RTX 4090, pcieInterface, PCIe 4.0 x16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pcieInterface Context triple: [NVIDIA GeForce RTX 4090, pcieInterface, PCIe 4.0 x16]
-
A.
supportsPCIeVersion
chosen
Indicates that one entity is compatible with or able to operate using a specified version of the PCI Express (PCIe) standard.
-
B.
maxPCIeLanesPerSocket
Indicates the maximum number of PCIe lanes that a single processor socket can support.
-
C.
hasMiniPCI
Indicates that one entity is equipped with or includes a Mini PCI (Peripheral Component Interconnect) interface or slot.
-
D.
interconnectTechnology
Indicates a relationship where different technologies are linked or integrated so they can work together or share information.
-
E.
primaryLimitationComparedToPCIe
Indicates the main constraint or drawback of something when it is compared specifically to PCIe.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8e631d88190aa2d39f7f485c1b8 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:45 p.m.