Triple

T1808652
Position Surface form Disambiguated ID Type / Status
Subject RFC 2818 E40278 entity
Predicate relatedTo P37 FINISHED
Object SSL E35266 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: SSL | Statement: [RFC 2818, relatedTo, SSL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SSL
Context triple: [RFC 2818, relatedTo, SSL]
  • A. SSL chosen
    SSL (Secure Sockets Layer) is a cryptographic protocol designed to provide secure, encrypted communication over a computer network, commonly used to protect data transmitted between clients and servers.
  • B. TLS
    TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
  • C. HTTPS
    HTTPS is the secure version of the HTTP protocol that encrypts data exchanged between a client and server to protect confidentiality and integrity on the web.
  • D. LE Secure Connections
    LE Secure Connections is an enhanced Bluetooth Low Energy security feature that provides stronger encryption and protection against eavesdropping and man-in-the-middle attacks during device pairing and data exchange.
  • E. HTTPS Everywhere
    HTTPS Everywhere is a browser extension that automatically enforces secure, encrypted HTTPS connections to websites to protect users’ privacy and security online.
  • 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_69a88643a3388190a612f2ebe1fb29e7 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa6599f35c8190aefd20773365fdcf completed March 6, 2026, 5:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69adead39c208190aa3aaf793c7e3224 completed March 8, 2026, 9:32 p.m.
Created at: March 4, 2026, 7:32 p.m.