Triple

T8052819
Position Surface form Disambiguated ID Type / Status
Subject Intel Core i3-10100Y E187714 entity
Predicate supportsIntelOSGuard P80766 FINISHED
Object yes 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: yes | Statement: [Intel Core i3-10100Y, supportsIntelOSGuard, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsIntelOSGuard
Context triple: [Intel Core i3-10100Y, supportsIntelOSGuard, yes]
  • A. hasHardwareCompatibilityWith
    Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
  • B. supportsSecureBoot
    Indicates that an entity is capable of enabling or operating with secure boot mechanisms that verify software integrity during the startup process.
  • C. hasSoftwareCompatibilityWith
    Indicates that one software system can operate correctly and effectively with another software system, without conflicts or required modifications.
  • D. supportsMemoryProtection
    Indicates that one entity provides mechanisms to prevent unauthorized access or interference with another entity’s memory space.
  • E. isPartOfSystemProtecting
    Indicates that one entity functions as a component within a larger system whose purpose is to provide protection.
  • 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_69ca82b15e948190a62fd7af5218426a completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3f7c425c8190aa1b2f534afeb58c completed March 31, 2026, 3:29 a.m.
PD Predicate disambiguation batch_69cb049a1b9c8190811c396421ebf9c9 completed March 30, 2026, 11:17 p.m.
PDg Predicate description generation batch_69cb14bcbbc0819094a98e7ffffb7a40 completed March 31, 2026, 12:26 a.m.
Created at: March 30, 2026, 5:25 p.m.