Triple
T23487186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE microwave band designations |
E570566
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | frequency band designation system |
C19970
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: frequency band designation system Context triple: [IEEE microwave band designations, instanceOf, frequency band designation system]
-
A.
radio frequency band
chosen
A radio frequency band is a specific range of electromagnetic spectrum frequencies allocated for particular types of wireless communication or broadcasting services.
-
B.
radiotelephony designator
A radiotelephony designator is a standardized spoken identifier assigned to an aircraft operator, airline, or aviation service for use in voice radio communications.
-
C.
scatter band
A scatter band is a visual representation on a chart that shows the range and distribution of data points around a central trend, typically using shaded regions or boundaries to indicate variability or uncertainty.
-
D.
frequency-hopping communication system
A frequency-hopping communication system is a wireless transmission method in which the carrier rapidly switches among multiple frequency channels according to a pseudorandom sequence shared by transmitter and receiver to enhance security and resistance to interference.
-
E.
frequency synchronization equipment
Frequency synchronization equipment is a class of devices that generate, distribute, and align timing signals to ensure multiple systems or components operate at a common, stable frequency reference.
- F. None of above.
Provenance (1 batch)
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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:04 p.m.