Triple
T5479734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDD |
E123440
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | wireless communication technique |
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: wireless communication technique Context triple: [FDD, instanceOf, wireless communication technique]
-
A.
wireless communication device
A wireless communication device is an electronic apparatus that transmits and receives data over radio or other non-wired signals to enable voice, text, or multimedia communication without physical connections.
-
B.
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.
-
C.
telecommunications standard
A telecommunications standard is an agreed-upon set of technical specifications and protocols that ensure compatibility, interoperability, and reliable communication across different telecom networks and devices.
-
D.
telecommunications patent
A telecommunications patent is a legal protection granted for an invention that enables or improves the transmission, routing, or processing of information over communication networks and systems.
-
E.
data connectivity technology
Data connectivity technology encompasses the tools, protocols, and infrastructure that enable seamless, secure, and reliable exchange of data between systems, applications, and devices across diverse networks and environments.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:09 p.m.