Triple
T54026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP/1.1 |
E1064
|
entity |
| Predicate | successorOf |
P78
|
FINISHED |
| Object | HTTP/1.0 |
E1064
|
NE FINISHED |
How this triple was built (2 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: HTTP/1.0 | Statement: [HTTP/1.1, successorOf, HTTP/1.0]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HTTP/1.0 Context triple: [HTTP/1.1, successorOf, HTTP/1.0]
-
A.
HTTP
chosen
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
B.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
C.
Telnet
Telnet is a network protocol and command-line tool that allows users to remotely access and manage devices over a text-based terminal connection.
-
D.
SSL 3.0
SSL 3.0 is an obsolete cryptographic protocol that once secured internet communications and served as the foundation for the early versions of TLS.
-
E.
POP3
POP3 (Post Office Protocol version 3) is a standard email protocol used by clients to retrieve messages from a remote mail server over a TCP/IP network, typically downloading them for local storage.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b04ef708190876686da9db1f04d |
completed | Feb. 28, 2026, 1:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a25ab66dd0819081443ebc4702d3b0 |
completed | Feb. 28, 2026, 3:02 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.