Triple
T26377463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Predator |
E660938
|
entity |
| Predicate | usesGPUFrom |
P109515
|
FINISHED |
| Object | NVIDIA |
—
|
NE NERFINISHED |
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: NVIDIA | Statement: [Predator, usesGPUFrom, NVIDIA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGPUFrom Context triple: [Predator, usesGPUFrom, NVIDIA]
-
A.
supportsGPUType
Indicates that one entity is compatible with, or capable of operating using, a specified type of GPU.
-
B.
integratesGPU
Indicates that one entity incorporates or embeds a GPU as a functional component within its design or system.
-
C.
suppliedGPUFor
chosen
Indicates that one entity provided or furnished a GPU to another entity for its use or operation.
-
D.
supportsExternalGPU
Indicates that an entity is capable of working with or providing connectivity for an external graphics processing unit (eGPU).
-
E.
usesNumberOfGPUs
Indicates that an entity operates with, depends on, or is configured to utilize a specified number of GPUs.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61071a4c4819090729e0c9789cf21 |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:02 p.m.