Triple

T27885336
Position Surface form Disambiguated ID Type / Status
Subject Intel Core m3-7Y30 E705207 entity
Predicate supportsIntelHyperThreadingTechnology P80134 FINISHED
Object true 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: true | Statement: [Intel Core m3-7Y30, supportsIntelHyperThreadingTechnology, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsIntelHyperThreadingTechnology
Context triple: [Intel Core m3-7Y30, supportsIntelHyperThreadingTechnology, true]
  • A. supportsIntelHyperThreading chosen
    Indicates that one entity provides compatibility with or functionality for Intel Hyper-Threading technology in relation to another entity.
  • B. supportsHyperThreading
    Indicates that one entity provides or enables Hyper-Threading capability for another entity.
  • C. supportsIntelTurboBoost
    Indicates that one entity provides compatibility with or functional support for Intel Turbo Boost technology in relation to another entity.
  • D. supportsDualProcessors
    Indicates that an entity is capable of operating with or accommodating two processors simultaneously.
  • E. supportsProcessorCoreCount
    Indicates that one entity is compatible with or able to operate using a specified number of processor cores in another entity.
  • F. None of above.

Provenance (3 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_69ef96b39c448190a9b3aa6672a5168f completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_6a0031ed5d708190ab93516ad081ada6 completed May 10, 2026, 7:21 a.m.
PD Predicate disambiguation batch_6a0031b5dbd081908eb0f4dbb8a0eac3 completed May 10, 2026, 7:20 a.m.
Created at: April 27, 2026, 6:32 p.m.