Triple

T17519440
Position Surface form Disambiguated ID Type / Status
Subject OpenAPI Specification E426647 entity
Predicate supportsProtocol P203 FINISHED
Object HTTPS NE NERFINISHED

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: HTTPS | Statement: [OpenAPI Specification, supportsProtocol, HTTPS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HTTPS
Context triple: [OpenAPI Specification, supportsProtocol, HTTPS]
  • A. HTTPS chosen
    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.
  • B. SSL
    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.
  • C. SSL
    SSL is a satellite manufacturing company known for building commercial communications and Earth observation spacecraft.
  • D. HTTPS Everywhere
    HTTPS Everywhere is a browser extension that automatically enforces secure, encrypted HTTPS connections to websites to protect users’ privacy and security online.
  • E. SSL/TLS
    SSL/TLS is a widely used cryptographic protocol suite that provides secure, encrypted communication over computer networks, most notably for web traffic.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889de677081909b22d2657b1f0292 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e452d18c1c81908bb843bbddb44ca1 completed April 19, 2026, 3:58 a.m.
Created at: April 10, 2026, 5:49 a.m.