Triple
T1881548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPDY |
E39862
|
entity |
| Predicate | influenced |
P9
|
FINISHED |
| Object | RFC 7540 (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: RFC 7540 (HTTP/2 specification) | Statement: [SPDY, influenced, RFC 7540 (HTTP/2 specification)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 7540 (HTTP/2 specification) Context triple: [SPDY, influenced, RFC 7540 (HTTP/2 specification)]
-
A.
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.
-
B.
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.
-
C.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
D.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
E.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0fb95b48190af5286662c8b9734 |
completed | March 7, 2026, 5 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69addf5eabd8819089f267db92993033 |
completed | March 8, 2026, 8:43 p.m. |
Created at: March 4, 2026, 7:34 p.m.