Triple
T8918024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mintDrivers |
E212340
|
entity |
| Predicate | handlesHardware |
P86384
|
FINISHED |
| Object | graphics adapters |
—
|
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: graphics adapters | Statement: [mintDrivers, handlesHardware, graphics adapters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesHardware Context triple: [mintDrivers, handlesHardware, graphics adapters]
-
A.
checksHardware
Indicates that one entity inspects or verifies the condition, presence, or correctness of another entity’s hardware components.
-
B.
runsOnHardware
Indicates that a system, software, or process operates using or is executed on a specified hardware platform.
-
C.
hardwareFinish
Indicates the type or style of surface treatment or coating applied to a piece of hardware.
-
D.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
E.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66120eb08190913ab6c42f26ffb8 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc600a59708190ae426044bbcd7929 |
completed | April 1, 2026, midnight |
Created at: March 30, 2026, 6:56 p.m.