Triple

T4275608
Position Surface form Disambiguated ID Type / Status
Subject Vapor E97041 entity
Predicate supportsProtocol P203 FINISHED
Object HTTP E1064 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: HTTP | Statement: [Vapor, supportsProtocol, HTTP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HTTP
Context triple: [Vapor, supportsProtocol, HTTP]
  • A. HTTP chosen
    HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
  • B. HTTP/1.1
    HTTP/1.1 is a widely used version of the Hypertext Transfer Protocol that introduced persistent connections, chunked transfer encoding, and improved caching mechanisms for web communication.
  • C. 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.
  • D. HAL (Hypertext Application Language)
    HAL (Hypertext Application Language) is a simple, JSON-based hypermedia format that standardizes how to represent and navigate links and embedded resources in RESTful APIs.
  • E. 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.
  • 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_69b34544be3c819084d1ab82d29f90c5 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3501c35688190a7d15d904f15f968 completed March 12, 2026, 11:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5c7237b608190ab5aca56027344c4 completed March 14, 2026, 8:37 p.m.
Created at: March 12, 2026, 11:07 p.m.