Triple
T8816725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NPN (Next Protocol Negotiation) |
E209794
|
entity |
| Predicate | replacedBy |
P101
|
FINISHED |
| Object | ALPN (Application-Layer Protocol Negotiation) |
E209795
|
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: ALPN (Application-Layer Protocol Negotiation) | Statement: [NPN (Next Protocol Negotiation), replacedBy, ALPN (Application-Layer Protocol Negotiation)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ALPN (Application-Layer Protocol Negotiation) Context triple: [NPN (Next Protocol Negotiation), replacedBy, ALPN (Application-Layer Protocol Negotiation)]
-
A.
ALPN (Application-Layer Protocol Negotiation)
chosen
ALPN (Application-Layer Protocol Negotiation) is a TLS extension that allows clients and servers to agree on which application-layer protocol (such as HTTP/2 or SPDY) to use over a secure connection during the TLS handshake.
-
B.
NPN (Next Protocol Negotiation)
NPN (Next Protocol Negotiation) is a now-deprecated TLS extension that allowed a client and server to agree on which application-layer protocol (such as SPDY or HTTP/2) to use over a secure connection.
-
C.
AT-TLS (Application Transparent TLS)
AT-TLS (Application Transparent TLS) is an IBM z/OS networking function that transparently provides TLS encryption and decryption for application traffic without requiring changes to the applications themselves.
-
D.
Server Name Indication extension
The Server Name Indication (SNI) extension is a TLS protocol feature that allows a client to indicate the hostname it is trying to connect to at the start of the handshake so that the server can present the correct certificate for virtual hosting.
-
E.
QUIC TLS usage specification
The QUIC TLS usage specification is an IETF document that defines how the QUIC transport protocol integrates and uses TLS for secure, encrypted internet communication.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600bd8a88190ad891a96201d796b |
completed | April 1, 2026, midnight |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6fc1579c8190ade0f780183aa1dc |
completed | April 3, 2026, 7:44 a.m. |
Created at: March 30, 2026, 6:46 p.m.