Triple
T25310827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAC-in-MAC |
E634602
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ethernet encapsulation mechanism |
C21903
|
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: Ethernet encapsulation mechanism Context triple: [MAC-in-MAC, instanceOf, Ethernet encapsulation mechanism]
-
A.
IP encapsulation mechanism
An IP encapsulation mechanism is a method by which one IP packet is wrapped inside another protocol header (often another IP header) to enable tunneling, virtualization, or transport across differing network infrastructures.
-
B.
VLAN encapsulation mechanism
chosen
A VLAN encapsulation mechanism is a method of tagging or wrapping Ethernet frames with VLAN identifiers (such as 802.1Q tags) to logically separate and manage network traffic across shared physical infrastructure.
-
C.
link-layer protocol
A link-layer protocol defines the rules and procedures for reliable data transfer, framing, addressing, and error handling between directly connected network devices on a physical medium.
-
D.
Ethernet fronthaul standard
An Ethernet fronthaul standard defines the protocols, interfaces, and performance requirements for transporting radio access network (RAN) traffic between distributed radio units and centralized baseband units over Ethernet-based networks.
-
E.
IEEE 802.2 LLC field
The IEEE 802.2 LLC field is a header component in data link layer frames that provides logical link control functions such as addressing, flow control, and error notification between network devices.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:26 p.m.