Effective address has nothing to do with paging or segmentation. It simply means the actual final numerical address that is calculated from an instruction that uses variables or arithmetic in the address operand, eg indexing or scaling.
If you are in protected mode with paging then the EA is still an address in your virtual memory map / linear address space before the page and segment translation occur.
Compare
Mov EAX, [0x1000000C]
Vs
Mov EBX , 0x10000000
Mov EDI , 3
Mov EAX, [EBX +EDI*4]
Both produce a virtual address of 0x1000000C with respect to the applications linear memory map (which is really not linear and undergoes page and segment translation to generate a physical address).
But the second method has to do an effective address calculation to resolve the unknown virtul address.
In 16 bit real mode LEA is an r16 instruction so it only computes the offset portion of the segment : offset addressing.
As for terminology:
Effective address = the resulting linear/virtual address as a result of an opcode that uses arithmetic to generate an offset instead of an immediate absolute value.
Linear address = virtual address = what an application sees, generates, and uses, completely oblivious to any paging or segmentation mechanisms. All EAs are linear/virtual addresses within the applications own memory map. When we say linear address we mean virtual address because it is page tables that give the illusion of linear memory by organizing non contiguous blocks of physical memory in consecutive page table entries.
Physical address = after paging and segmentation translations, what appears on the CPUs external A00 -Ann pins.