Triple
T31025469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autodesk Arnold GPU |
E790555
|
entity |
| Predicate | usesHardwareVendor |
P170924
|
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: [Autodesk Arnold GPU, usesHardwareVendor, NVIDIA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHardwareVendor Context triple: [Autodesk Arnold GPU, usesHardwareVendor, NVIDIA]
-
A.
supportsHardwareVendor
Indicates that one entity provides assistance, resources, or endorsement to a hardware vendor in fulfilling its products or services.
-
B.
osVendor
Indicates that one entity is the vendor or provider of an operating system associated with another entity.
-
C.
supportsVendor
Indicates that one entity provides assistance, resources, or endorsement to a vendor in carrying out its activities or services.
-
D.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
E.
hasHardware
Indicates that one entity possesses, includes, or is equipped with specific hardware components or devices.
- F. None of above. chosen
Provenance (4 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:58 p.m.