Triple
T2175112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebSockets Standard |
E48508
|
entity |
| Predicate | isDefinedBy |
P4728
|
FINISHED |
| Object |
IETF RFC 6455
IETF RFC 6455 is the core specification that defines the WebSocket protocol, enabling full-duplex, persistent communication between web clients and servers over a single TCP connection.
|
E48508
|
NE FINISHED |
How this triple was built (4 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: IETF RFC 6455 | Statement: [WebSockets Standard, isDefinedBy, IETF RFC 6455]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IETF RFC 6455 Context triple: [WebSockets Standard, isDefinedBy, IETF RFC 6455]
-
A.
WebSockets Standard
The WebSockets Standard is a web technology specification that enables full-duplex, real-time communication between web browsers and servers over a single, long-lived connection.
-
B.
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.
-
C.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
D.
RFC 7540
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.
-
E.
RFC 8259
RFC 8259 is the IETF specification that formally defines the JSON (JavaScript Object Notation) data interchange format, including its syntax and semantics.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: IETF RFC 6455 Triple: [WebSockets Standard, isDefinedBy, IETF RFC 6455]
Generated description
IETF RFC 6455 is the core specification that defines the WebSocket protocol, enabling full-duplex, persistent communication between web clients and servers over a single TCP connection.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: IETF RFC 6455 Target entity description: IETF RFC 6455 is the core specification that defines the WebSocket protocol, enabling full-duplex, persistent communication between web clients and servers over a single TCP connection.
-
A.
WebSockets Standard
chosen
The WebSockets Standard is a web technology specification that enables full-duplex, real-time communication between web browsers and servers over a single, long-lived connection.
-
B.
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.
-
C.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
D.
RFC 7540
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.
-
E.
RFC 8259
RFC 8259 is the IETF specification that formally defines the JSON (JavaScript Object Notation) data interchange format, including its syntax and semantics.
- F. None of above.
Provenance (5 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbeccb2888190aa1fe1039e9dfbe2 |
completed | March 7, 2026, 5:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae5d9eff988190a02734bd73616cba |
completed | March 9, 2026, 5:41 a.m. |
| NEDg | Description generation | batch_69ae5e5f023081909cd046b5850f8026 |
completed | March 9, 2026, 5:45 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae5ef99018819083a778378ea493e8 |
completed | March 9, 2026, 5:47 a.m. |
Created at: March 4, 2026, 7:45 p.m.