Triple
T2187925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTTP Working Group |
E49793
|
entity |
| Predicate | responsibleFor |
P636
|
FINISHED |
| Object | HTTP/2 specification |
E206428
|
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/2 specification | Statement: [HTTP Working Group, responsibleFor, HTTP/2 specification]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HTTP/2 specification Context triple: [HTTP Working Group, responsibleFor, HTTP/2 specification]
-
A.
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.
-
B.
RFC 7540
chosen
RFC 7540 is the Internet Engineering Task Force (IETF) standard that defines HTTP/2, the major revision of the Hypertext Transfer Protocol designed to improve web performance and efficiency.
-
C.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
D.
QUIC TLS usage specification
The QUIC TLS usage specification is an IETF document that defines how the QUIC transport protocol integrates and uses TLS for secure, encrypted internet communication.
-
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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf130ef081908adb4a22f056be5b |
completed | March 7, 2026, 6 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae5dada268819082ddc4acd58e19f3 |
completed | March 9, 2026, 5:42 a.m. |
Created at: March 4, 2026, 7:45 p.m.