Network Control Protocol
E4674
Network Control Protocol was an early host-to-host communication protocol that formed the basis of data transmission on the ARPANET before the adoption of TCP/IP.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Network Control Program | 4 |
| Network Control Protocol canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T52558 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: Network Control Protocol Context triple: [ARPANET, usedProtocol, Network Control Protocol]
-
A.
Network Control Center
The Network Control Center is a centralized facility responsible for monitoring, managing, and coordinating the operation of a computer or communications network.
-
B.
TCP/IP
TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer networks.
-
C.
IEEE 802.1D MAC bridging standard
The IEEE 802.1D MAC bridging standard is a networking specification that defines how Ethernet bridges and switches forward frames and prevent loops in local area networks, including the original Spanning Tree Protocol.
-
D.
IEEE 802.1Qcx YANG data model for bridge management standard
The IEEE 802.1Qcx YANG data model for bridge management standard defines a structured, machine-readable configuration and management model for Ethernet bridges to support automated and interoperable network management.
-
E.
IEEE 802.1Q VLAN tagging standard
The IEEE 802.1Q VLAN tagging standard defines how virtual LANs are implemented and identified over Ethernet networks by inserting a VLAN tag into Ethernet frames.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: Network Control Protocol Target entity description: Network Control Protocol was an early host-to-host communication protocol that formed the basis of data transmission on the ARPANET before the adoption of TCP/IP.
-
A.
Network Control Center
The Network Control Center is a centralized facility responsible for monitoring, managing, and coordinating the operation of a computer or communications network.
-
B.
TCP/IP
TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer networks.
-
C.
IEEE 802.1D MAC bridging standard
The IEEE 802.1D MAC bridging standard is a networking specification that defines how Ethernet bridges and switches forward frames and prevent loops in local area networks, including the original Spanning Tree Protocol.
-
D.
IEEE 802.1Qcx YANG data model for bridge management standard
The IEEE 802.1Qcx YANG data model for bridge management standard defines a structured, machine-readable configuration and management model for Ethernet bridges to support automated and interoperable network management.
-
E.
IEEE 802.1Q VLAN tagging standard
The IEEE 802.1Q VLAN tagging standard defines how virtual LANs are implemented and identified over Ethernet networks by inserting a VLAN tag into Ethernet frames.
- F. None of above. chosen
Statements (40)
| Predicate | Object |
|---|---|
| instanceOf |
ARPANET protocol
ⓘ
communication protocol ⓘ host-to-host protocol ⓘ |
| abbreviation | NCP ⓘ |
| basedOn | Interface Message Processor network services ⓘ |
| category |
computer networking
ⓘ
internet history ⓘ |
| contrastWith | internetworking capabilities of TCP/IP ⓘ |
| designedFor | time-sharing computer systems ⓘ |
| developedFor |
Advanced Research Projects Agency Network
ⓘ
surface form:
United States Department of Defense ARPANET project
|
| followedBy | TCP/IP ⓘ |
| function |
handled error control
ⓘ
handled flow control ⓘ managed connections between ARPANET hosts ⓘ multiplexed multiple logical connections over a single ARPANET link ⓘ provided host-to-host communication services ⓘ |
| historicalRole |
early example of a transport-like protocol
ⓘ
formed the basis of data transmission on the ARPANET before TCP/IP ⓘ |
| implements |
basic flow control mechanisms
ⓘ
connection establishment procedures ⓘ connection termination procedures ⓘ |
| influenced |
design of TCP
ⓘ
early internet architecture ⓘ |
| layer | host-to-host layer ⓘ |
| networkType | packet-switched network ⓘ |
| operatedOver |
MILNET
ⓘ
surface form:
Interface Message Processor subnetwork
|
| partOf | ARPANET protocol suite ⓘ |
| predecessorOf | TCP/IP ⓘ |
| replacedBy |
Internet Protocol
ⓘ
Transmission Control Protocol ⓘ |
| scope | single ARPANET network ⓘ |
| standardizedIn |
RFCs
ⓘ
surface form:
ARPANET Request for Comments
|
| status | obsolete ⓘ |
| supports |
full-duplex connections
ⓘ
multiple simultaneous connections between host pairs ⓘ reliable data transfer between hosts ⓘ |
| timePeriod |
1970s
ⓘ
late 1960s ⓘ |
| usedOn | ARPANET ⓘ |
| uses | 8-bit connection identifiers ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: Network Control Protocol Description of subject: Network Control Protocol was an early host-to-host communication protocol that formed the basis of data transmission on the ARPANET before the adoption of TCP/IP.
Referenced by (7)
Full triples — surface form annotated when it differs from this entity's canonical label.