Triple

T25741600
Position Surface form Disambiguated ID Type / Status
Subject Raptor Lake Refresh E648230 entity
Predicate supportsOverclocking P189701 FINISHED
Object yes (on K and KF SKUs) 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 (on K and KF SKUs) | Statement: [Raptor Lake Refresh, supportsOverclocking, yes (on K and KF SKUs)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsOverclocking
Context triple: [Raptor Lake Refresh, supportsOverclocking, yes (on K and KF SKUs)]
  • A. supportsIntelTurboBoost
    Indicates that one entity provides compatibility with or functional support for Intel Turbo Boost technology in relation to another entity.
  • B. supportsTurboBoost
    Indicates that one entity provides or is compatible with Turbo Boost functionality for another entity or process.
  • C. hasClockSpeed
    Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
  • D. supportsIntelSpeedStep
    Indicates that an entity provides compatibility with or functionality for Intel SpeedStep power management technology.
  • E. supportsIntelSpeedShift
    Indicates that one entity provides compatibility with or enables the Intel Speed Shift power/performance management technology for another entity.
  • 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_69e7ab306eec8190b05c312c6ab186b8 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69fbca6c066c8190a1599202f341417f completed May 6, 2026, 11:10 p.m.
PD Predicate disambiguation batch_69fbc8ec03ac8190a757563f96fab283 completed May 6, 2026, 11:04 p.m.
PDg Predicate description generation batch_69fbc9d0854c8190aa00093274afebb8 completed May 6, 2026, 11:08 p.m.
Created at: April 22, 2026, 3:45 a.m.