Triple

T29405027
Position Surface form Disambiguated ID Type / Status
Subject KMS (Kernel Mode Setting) E745757 entity
Predicate supportsDrivers P201942 FINISHED
Object Intel DRM driver E1682202 NE 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: Intel DRM driver | Statement: [KMS (Kernel Mode Setting), supportsDrivers, Intel DRM driver]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsDrivers
Context triple: [KMS (Kernel Mode Setting), supportsDrivers, Intel DRM driver]
  • A. supportsDriverType
    Indicates that one entity is compatible with, or able to operate using, a specified type of driver.
  • B. supportsDriverModel chosen
    Indicates that one entity provides compatibility with, or operational backing for, a specified driver model used to interface with hardware or software components.
  • C. developedDriversFor
    Indicates that one entity created or produced software drivers to enable another entity’s hardware or system to function or be controlled.
  • D. supportedIn
    Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
  • E. supportsAt
    Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
  • F. None of above.

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_69f0a79eb7d081908c67197a5f347e68 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_6a0361c6d76481909332b28ab01b0ef7 completed May 12, 2026, 5:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25d91aa7cc819082409393cd289019 completed June 7, 2026, 8:48 p.m.
PD Predicate disambiguation batch_6a0360b3818c819084bbecf705475f4f completed May 12, 2026, 5:17 p.m.
Created at: April 28, 2026, 2:53 p.m.