Triple
T20221692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SC-FDMA |
E495270
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-carrier modulation scheme |
C17578
|
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: multi-carrier modulation scheme Context triple: [SC-FDMA, instanceOf, multi-carrier modulation scheme]
-
A.
multi-carrier modulation technique
chosen
A multi-carrier modulation technique is a method of transmitting data by dividing it across multiple closely spaced subcarriers, each modulated with a portion of the data stream to improve spectral efficiency and robustness against channel impairments.
-
B.
multi-mode radar
A multi-mode radar is a radar system capable of operating in several distinct modes (such as search, tracking, mapping, and weather detection) to support diverse sensing and mission requirements.
-
C.
family of digital subscriber line technologies
A family of digital subscriber line technologies is a group of related high-speed data transmission methods that use existing telephone lines to deliver broadband internet and other digital services.
-
D.
multispectral targeting system
A multispectral targeting system is an integrated sensor and processing suite that detects, tracks, and designates targets across multiple parts of the electromagnetic spectrum (e.g., visible, infrared, and radar) to enhance accuracy and situational awareness.
-
E.
media access control technique
A media access control technique is a method or protocol that governs how multiple devices share and coordinate access to a common communication medium to avoid collisions and ensure efficient data transmission.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:39 p.m.