Triple
T8822598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA GeForce GPU line |
E209941
|
entity |
| Predicate | typicalBusInterface |
P79786
|
FINISHED |
| Object | PCI Express |
—
|
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: PCI Express | Statement: [NVIDIA GeForce GPU line, typicalBusInterface, PCI Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBusInterface Context triple: [NVIDIA GeForce GPU line, typicalBusInterface, PCI Express]
-
A.
dataBusType
Indicates the type or category of data bus used to transfer data between components or systems.
-
B.
systemBus
Indicates a relationship where a component is connected to or communicates over a shared system-wide communication bus.
-
C.
primaryBus
Indicates that one entity functions as the main or principal bus associated with another entity within a system or configuration.
-
D.
supportsBusController
Indicates that one entity provides the necessary functionality or compatibility to operate, manage, or interface with a bus controller for another entity.
-
E.
hasBusArchitecture
chosen
Indicates that one entity uses, implements, or is characterized by a particular bus architecture in its design or operation.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc602ed87c8190ab772e5cbb2da68d |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:46 p.m.