Triple
T34541604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OsmoTRX |
E886820
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | software-defined radio transceiver |
C448
|
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: software-defined radio transceiver Context triple: [OsmoTRX, instanceOf, software-defined radio transceiver]
-
A.
radio transmitter
A radio transmitter is a device that generates, modulates, and emits radio-frequency signals through an antenna to convey information wirelessly over distance.
-
B.
IMT-2000 radio interface
An IMT-2000 radio interface is a standardized third-generation (3G) mobile communication air interface specification that defines how user equipment and networks exchange radio signals to provide global, interoperable wireless voice and data services.
-
C.
microwave radio system family
A microwave radio system family is a group of related microwave communication systems that share common architecture, components, and design principles to transmit high-frequency radio signals for point-to-point or point-to-multipoint links.
-
D.
radio receiver architecture
A radio receiver architecture is the conceptual design and organization of functional blocks and signal paths that determine how a receiver selects, downconverts, filters, and demodulates radio-frequency signals into usable information.
-
E.
wireless communication device
chosen
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.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.