Triple
T10926992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6066 |
E258094
|
entity |
| Predicate | defines |
P264
|
FINISHED |
| Object | SNI extension |
E258091
|
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: SNI extension | Statement: [RFC 6066, defines, SNI extension]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SNI extension Context triple: [RFC 6066, defines, SNI extension]
-
A.
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.
-
B.
SNI
chosen
SNI (Server Name Indication) is a TLS extension that allows a client to specify the hostname it is trying to connect to so that the server can present the correct SSL/TLS certificate for virtual hosting.
-
C.
ALPN (Application-Layer Protocol Negotiation)
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.
-
D.
ServerHello with extensions
ServerHello with extensions is a TLS handshake message variant that allows a server to include additional extension data to negotiate optional protocol features and capabilities with a client.
-
E.
TLS heartbeat extension (later deprecated)
The TLS heartbeat extension was a Transport Layer Security protocol feature designed to keep secure connections alive and test reachability, later becoming widely known for the critical Heartbleed vulnerability that led to its deprecation.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7709165188190aa30dd08deddade4 |
completed | April 9, 2026, 9:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e217475344819088b44b6efb2df1c8 |
completed | April 17, 2026, 11:19 a.m. |
Created at: April 8, 2026, 9:22 p.m.