Triple

T35698067
Position Surface form Disambiguated ID Type / Status
Subject CCIR System H E1031497 entity
Predicate soundToVisionCarrierSpacing P108609 FINISHED
Object 5.5 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: 5.5 MHz | Statement: [CCIR System H, soundToVisionCarrierSpacing, 5.5 MHz]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: soundToVisionCarrierSpacing
Context triple: [CCIR System H, soundToVisionCarrierSpacing, 5.5 MHz]
  • A. soundCarrierOffset chosen
    Indicates the positional or temporal displacement of a sound carrier relative to a defined reference point or baseline.
  • B. soundCarrier
    Indicates that one entity serves as a medium or object that carries, stores, or transmits sound for another entity.
  • C. hasToneFrequencyResolution
    Indicates that one entity specifies the smallest distinguishable difference in tone frequency that can be measured or represented by another entity.
  • D. modulationIndex
    Indicates the degree to which one signal or factor varies or controls another signal’s amplitude, frequency, or phase in a modulation process.
  • E. hasCarrierFrequency
    Indicates that an entity (such as a signal or transmission) is associated with a specific carrier frequency at which it is transmitted or modulated.
  • 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_69f76e0c73ec819080ab60a9e2f5f1f6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a34f8ee08190a040304635539a8f completed May 3, 2026, 7:34 p.m.
PD Predicate disambiguation batch_69f7a06f125c8190843af194f042a465 completed May 3, 2026, 7:22 p.m.
Created at: May 3, 2026, 4:05 p.m.