Triple

T5017218
Position Surface form Disambiguated ID Type / Status
Subject Oracle Virtual Directory E112763 entity
Predicate supportsProtocol P203 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: [Oracle Virtual Directory, supportsProtocol, SSL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SSL
Context triple: [Oracle Virtual Directory, supportsProtocol, 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 is the IATA airport code for Toulouse-Blagnac Airport, the main international airport serving Toulouse in southwestern France.
  • C. TLS
    TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
  • D. 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.
  • E. 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.
  • 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_69bd4434acb8819086679dbeccc2fe54 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd734037a88190a950db814412a023 completed March 20, 2026, 4:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69be9c5e06fc8190bdd875c04cefd789 completed March 21, 2026, 1:25 p.m.
Created at: March 20, 2026, 1:35 p.m.