Triple

T7928872
Position Surface form Disambiguated ID Type / Status
Subject TLS Working Group E184134 entity
Predicate responsibleFor P636 FINISHED
Object TLS SNI extension E258090 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: TLS SNI extension | Statement: [TLS Working Group, responsibleFor, TLS SNI extension]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TLS SNI extension
Context triple: [TLS Working Group, responsibleFor, TLS SNI extension]
  • A. Server Name Indication extension chosen
    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. 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.
  • C. SNI
    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.
  • D. 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.
  • E. TLS 1.2
    TLS 1.2 is a widely deployed version of the Transport Layer Security protocol that provides encrypted and authenticated communication over computer networks.
  • 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_69ca828fe7bc819090f52c88dcd72183 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3ac9ac4c819082cd2190fc3ce5a2 completed March 31, 2026, 3:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5c01602081908ea1af24785260ff completed March 31, 2026, 5:30 a.m.
Created at: March 30, 2026, 5:07 p.m.