Triple
T209100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network Control Protocol |
E4674
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | host-to-host protocol |
C1866
|
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: host-to-host protocol Context triple: [Network Control Protocol, instanceOf, host-to-host protocol]
-
A.
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.
-
B.
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.
-
C.
packet-switched protocol
A packet-switched protocol is a communication method that breaks data into discrete packets, routes them independently across a network, and reassembles them at the destination for efficient and robust data transfer.
-
D.
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.
-
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. chosen
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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.