Orbital Freight Ledger Expansion

An orbital transfer station keeps its freight ledger in a terse numeric form: every sale references a cargo module by a short code rather than its full name, which suits the station's own computers but is useless to the customs officers who read the printed manifest. The station also keeps a module directory that maps each code to the module's full name. You must expand the ledger into a readable manifest: for every sale entry, replace its module code with the module's name and drop the shipped-unit count entirely (customs only cares about the year and the price actually charged per unit), while keeping every entry in the exact order it appears in the ledger.

Input format

Line 1: two integers M and S — the number of entries in the module directory and the number of sale entries in the ledger. The next M lines each contain a module code and the module's name: moduleCode moduleName. The next S lines each describe one sale: saleId moduleCode year quantity price.

Output format

Print exactly S lines. For the i-th sale entry in the ledger (in input order), print moduleName year price, where moduleName is the name of the module referenced by that entry's moduleCode.

Constraints

• 1 <= M <= 10^4, 1 <= S <= 2*10^4
• Module codes are distinct integers in [1, 10^9].
• Every module name is 1 to 20 characters long and consists only of letters, digits, and hyphens (no spaces).
• 1 <= saleId <= 10^9 (sale ids need not be distinct and are not otherwise used)
• Every sale's moduleCode matches a code that appears in the module directory.
• 1 <= year <= 10000
• 1 <= quantity <= 10^6 (not used in the output)
• 0 <= price <= 10^6

2 4
100 Nova
200 Zephyr
1 100 2008 10 5000
2 100 2009 12 5000
7 200 2011 15 9000
3 200 2009 30 9000

Nova 2008 5000
Nova 2009 5000
Zephyr 2011 9000
Zephyr 2009 9000

1 1
50 Comet
9 50 2020 3 100

Comet 2020 100