Triple
T29938177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeForce 200 Series |
E760424
|
entity |
| Predicate | supportsMultiGPU |
P173514
|
FINISHED |
| Object | dual-GPU configurations |
—
|
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: dual-GPU configurations | Statement: [GeForce 200 Series, supportsMultiGPU, dual-GPU configurations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultiGPU Context triple: [GeForce 200 Series, supportsMultiGPU, dual-GPU configurations]
-
A.
usesNumberOfGPUs
Indicates that an entity operates with, depends on, or is configured to utilize a specified number of GPUs.
-
B.
supportsGPUType
Indicates that one entity is compatible with, or capable of operating using, a specified type of GPU.
-
C.
supportsExternalGPU
Indicates that an entity is capable of working with or providing connectivity for an external graphics processing unit (eGPU).
-
D.
multiGPUSolution
chosen
Indicates that a solution or configuration involves the coordinated use of multiple GPUs to perform computation or rendering tasks.
-
E.
supportsGPUBrand
Indicates that one entity is compatible with, or provides functional support for, a specified GPU brand.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 6:21 p.m.