Triple

T264654
Position Surface form Disambiguated ID Type / Status
Subject GitHub E5697 entity
Predicate supportsAuthenticationMethod P203 FINISHED
Object HTTPS E7608 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: HTTPS | Statement: [GitHub, supportsAuthenticationMethod, HTTPS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HTTPS
Context triple: [GitHub, supportsAuthenticationMethod, 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. 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. HTTP
    HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
  • D. HTTP/2
    HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
  • E. RFC 8446
    RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
  • 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_69a2587daeb081909591b9d30f80a271 completed Feb. 28, 2026, 2:52 a.m.
NER Named-entity recognition batch_69a25d8f9bbc8190a13841e4de093a66 completed Feb. 28, 2026, 3:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69a389ae45648190966804664bf4f861 completed March 1, 2026, 12:34 a.m.
Created at: Feb. 28, 2026, 2:56 a.m.