Triple
T21192541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RLC (Radio Link Control) protocol for UMTS |
E522246
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Data link layer protocol |
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: Data link layer protocol Context triple: [RLC (Radio Link Control) protocol for UMTS, instanceOf, Data link layer protocol]
-
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.
physical layer protocol
A physical layer protocol defines the electrical, mechanical, and signaling specifications that govern how raw bits are transmitted over a physical medium in a communication system.
-
D.
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.
-
E.
session layer protocol
A session layer protocol is a network communication protocol that establishes, manages, and terminates logical connections (sessions) between applications, handling dialog control, synchronization, and orderly data exchange.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:07 p.m.