Triple
T471948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP/1.1 |
E8577
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | HTTP protocol version |
C902
|
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: HTTP protocol version Context triple: [HTTP/1.1, instanceOf, HTTP protocol version]
-
A.
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.
-
B.
web protocol
chosen
A web protocol is a standardized set of rules and formats that govern how data is requested, transmitted, and received between clients and servers over the World Wide Web.
-
C.
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.
-
D.
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.
-
E.
application-layer protocol
An application-layer protocol defines the rules and formats for how software applications communicate and exchange data over a network, sitting at the top of the protocol stack to support end-user services.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.