Triple
T394709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Protocol |
E8957
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internet layer protocol |
C997
|
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: internet layer protocol Context triple: [Internet Protocol, instanceOf, internet layer protocol]
-
A.
network layer protocol
chosen
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.
-
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.
internet protocol suite
The internet protocol suite is a conceptual framework of layered communication protocols (including TCP/IP) that defines how data is formatted, addressed, transmitted, routed, and received across interconnected computer networks.
-
D.
Internet Protocol version
An Internet Protocol version is a specific iteration of the Internet Protocol standard that defines how data packets are formatted, addressed, transmitted, and routed across interconnected networks.
-
E.
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.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.