Triple
T52558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARPANET |
E1032
|
entity |
| Predicate | usedProtocol |
P1215
|
FINISHED |
| Object |
Network Control Protocol
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.
|
E4674
|
NE FINISHED |
How this triple was built (5 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Network Control Protocol | Statement: [ARPANET, usedProtocol, Network Control Protocol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
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.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Network Control Protocol Triple: [ARPANET, usedProtocol, Network Control Protocol]
Generated 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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
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
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedProtocol Context triple: [ARPANET, usedProtocol, Network Control Protocol]
-
A.
usesProtocolSuite
chosen
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
-
B.
protocol
Indicates that one entity defines or follows a specific set of rules or procedures governing how it interacts or communicates with another entity.
-
C.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
D.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
E.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- F. None of above.
Provenance (6 batches)
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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c709c248190bcd442c8d508e48c |
completed | Feb. 28, 2026, 2:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a255381a7c8190a48bee7032c622bb |
completed | Feb. 28, 2026, 2:38 a.m. |
| NEDg | Description generation | batch_69a255df7a1081909d709a7b507e0035 |
completed | Feb. 28, 2026, 2:41 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69a256a681248190ac260a6f61b3c946 |
completed | Feb. 28, 2026, 2:44 a.m. |
| PD | Predicate disambiguation | batch_69a24ac3c8dc819099849023bdaa35a9 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.