Triple

T1416905
Position Surface form Disambiguated ID Type / Status
Subject Intel Core processor family E31938 entity
Predicate hasPerformanceTier P11443 FINISHED
Object entry-level 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: entry-level | Statement: [Intel Core processor family, hasPerformanceTier, entry-level]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPerformanceTier
Context triple: [Intel Core processor family, hasPerformanceTier, entry-level]
  • A. playsInTopTier
    Indicates that an entity participates as a competitor in the highest-level division or league within a given sport or competitive system.
  • B. hasRankCategory chosen
    Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
  • C. hasAwardLevel
    Indicates that an entity possesses or has been assigned a specific level, tier, or rank within an award or recognition system.
  • D. hasRankingCategory
    Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
  • E. featuresPerformanceBy
    Indicates a relationship where something (such as an event, work, or production) includes or showcases a performance given by a particular performer or group.
  • 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_69a49919a994819086528951bc224775 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c403ccdc8190b2a5fda037b6ea34 completed March 1, 2026, 10:56 p.m.
PD Predicate disambiguation batch_69a4bf060b0081909ba00e6ac093a28b completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:59 p.m.