Triple
T7936167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebDAV |
E184293
|
entity |
| Predicate | definedInRFC |
P5655
|
FINISHED |
| Object |
RFC 4918
RFC 4918 is the IETF specification that standardizes the Web Distributed Authoring and Versioning (WebDAV) extensions to HTTP for collaborative web content authoring and file management.
|
E699617
|
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: RFC 4918 | Statement: [WebDAV, definedInRFC, RFC 4918]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4918 Context triple: [WebDAV, definedInRFC, RFC 4918]
-
A.
RFC 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
B.
RFC 2817
RFC 2817 is an Internet standard that specifies how to use the HTTP/1.1 Upgrade mechanism to establish Transport Layer Security (TLS) over an existing HTTP connection.
-
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 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
-
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. 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: RFC 4918 Triple: [WebDAV, definedInRFC, RFC 4918]
Generated description
RFC 4918 is the IETF specification that standardizes the Web Distributed Authoring and Versioning (WebDAV) extensions to HTTP for collaborative web content authoring and file management.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 4918 Target entity description: RFC 4918 is the IETF specification that standardizes the Web Distributed Authoring and Versioning (WebDAV) extensions to HTTP for collaborative web content authoring and file management.
-
A.
RFC 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
B.
RFC 2817
RFC 2817 is an Internet standard that specifies how to use the HTTP/1.1 Upgrade mechanism to establish Transport Layer Security (TLS) over an existing HTTP connection.
-
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 5849
RFC 5849 is the Internet standard that originally defined the OAuth 1.0 protocol for secure delegated authorization before being superseded by OAuth 2.0 in RFC 6749.
-
E.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
- F. None of above. chosen
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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aede3cc81908b0d3b54e68997b9 |
completed | March 31, 2026, 3:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5c0791e48190af18299c22f6a804 |
completed | March 31, 2026, 5:30 a.m. |
| NEDg | Description generation | batch_69cb7634f4dc8190b5e537f24bccd651 |
completed | March 31, 2026, 7:22 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69cbb67e77a48190b93c6ba61becfac4 |
completed | March 31, 2026, 11:56 a.m. |
Created at: March 30, 2026, 5:08 p.m.