Triple
T9691006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3 MAC frame |
E234533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ethernet frame format |
C7819
|
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 frame format Context triple: [IEEE 802.3 MAC frame, instanceOf, Ethernet frame format]
-
A.
link-layer protocol
chosen
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.
-
B.
network layer protocol
A network layer protocol defines the rules and mechanisms for routing and forwarding data packets across interconnected networks, providing logical addressing and path selection between source and destination hosts.
-
C.
VLAN encapsulation mechanism
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.
-
D.
network protocol
A network protocol is a standardized set of rules and formats that enable computers and devices to communicate and exchange data reliably over a network.
-
E.
Fibre Channel protocol
Fibre Channel protocol is a high-speed network communication protocol primarily used to connect computer data storage to servers in storage area networks (SANs), providing reliable, lossless, and low-latency data transfer.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:17 p.m.