Triple
T20339499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Patent 2,292,387 |
E495701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | frequency-hopping communication patent |
C9329
|
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-hopping communication patent Context triple: [U.S. Patent 2,292,387, instanceOf, frequency-hopping communication patent]
-
A.
telecommunications patent
chosen
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.
-
B.
multi-carrier modulation technique
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.
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.
-
D.
RFID air interface standard
An RFID air interface standard defines the communication protocols, signal characteristics, and data exchange rules between RFID tags and readers over the wireless radio frequency link.
-
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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:23 a.m.