Triple
T36553521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PPP over Secure Shell (SSH) |
E901636
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | network tunneling protocol |
C901
|
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: network tunneling protocol Context triple: [PPP over Secure Shell (SSH), instanceOf, network tunneling protocol]
-
A.
network security protocol
A network security protocol is a defined set of rules and procedures that protect data integrity, confidentiality, and authenticity during communication between devices over a network.
-
B.
network protocol
chosen
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.
-
C.
tunneling system
A tunneling system is a conceptual framework or infrastructure that enables data, particles, or signals to pass through barriers or intermediate layers via a protected or probabilistic pathway without directly traversing the intervening space in a conventional manner.
-
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.
network protocol feature
A network protocol feature is a specific capability or mechanism within a communication protocol that defines how data is formatted, transmitted, managed, or secured between networked devices.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.