Triple

T25425838
Position Surface form Disambiguated ID Type / Status
Subject Socket 8 E637112 entity
Predicate typicalFSBFrequency P192624 FINISHED
Object 60 MHz 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: 60 MHz | Statement: [Socket 8, typicalFSBFrequency, 60 MHz]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalFSBFrequency
Context triple: [Socket 8, typicalFSBFrequency, 60 MHz]
  • A. frequencyBand
    Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
  • B. frequencyStandard
    Indicates that one entity serves as the reference or baseline frequency against which another entity’s frequency is defined, measured, or calibrated.
  • C. carrierFrequency
    Indicates the frequency at which a carrier signal or carrier wave operates in a communication or modulation process.
  • D. typicalFrequencyUnit
    Indicates the unit of measurement typically used to express the frequency of an event, action, or occurrence.
  • E. hasBroadcastFrequency
    Indicates that an entity operates or transmits at a specified broadcast frequency.
  • 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_69e75db58a1c8190891b9ff7c2f8414e completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69fd231cab588190ad0953dc8f4af8f2 completed May 7, 2026, 11:41 p.m.
PD Predicate disambiguation batch_69fd1aa3f1c481909fe6e9cab1383551 completed May 7, 2026, 11:05 p.m.
PDg Predicate description generation batch_69fd231bdd108190900369e07c854e95 completed May 7, 2026, 11:41 p.m.
Created at: April 21, 2026, 1:57 p.m.