Triple
T5066502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.1AB |
E114156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | link layer protocol specification |
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: link layer protocol specification Context triple: [IEEE 802.1AB, instanceOf, link layer protocol specification]
-
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.
transport layer protocol
A transport layer protocol is a communication protocol that provides end-to-end data transfer services between applications across networked devices, handling functions like segmentation, reliability, flow control, and multiplexing.
-
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.
communication protocol suite
A communication protocol suite is a coordinated set of network protocols that work together across different layers to enable reliable data exchange between devices in a communication system.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:38 p.m.