Triple

T10437063
Position Surface form Disambiguated ID Type / Status
Subject E-band systems E246071 entity
Predicate electromagneticSpectrumRegion P7244 FINISHED
Object millimeter wave 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: millimeter wave | Statement: [E-band systems, electromagneticSpectrumRegion, millimeter wave]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: electromagneticSpectrumRegion
Context triple: [E-band systems, electromagneticSpectrumRegion, millimeter wave]
  • A. spectralRegion chosen
    Indicates the portion of the electromagnetic spectrum (e.g., wavelength or frequency range) in which a measurement, observation, or property is defined or applies.
  • B. frequencyRegion
    Indicates that something is associated with, occurs within, or is characterized by a particular range or band of frequencies.
  • C. frequencyBand
    Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
  • D. emitsSpectrum
    Indicates that one entity produces or gives off electromagnetic radiation characterized by a particular spectrum.
  • E. observingBand
    Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
  • 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_69d381bf3dc08190bf35a2643e4e8f22 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4ea853c308190be95ae8dffe67ac1 completed April 7, 2026, 11:29 a.m.
PD Predicate disambiguation batch_69d4dfbc546881908f312c66ee195f79 completed April 7, 2026, 10:43 a.m.
Created at: April 6, 2026, 12:14 p.m.