Triple
T8672374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2617 |
E205827
|
entity |
| Predicate | definesHeaderField |
P3703
|
FINISHED |
| Object |
Proxy-Authorization
Proxy-Authorization is an HTTP request header used to provide credentials for authenticating a client to a proxy server.
|
E748453
|
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: Proxy-Authorization | Statement: [RFC 2617, definesHeaderField, Proxy-Authorization]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Proxy-Authorization Context triple: [RFC 2617, definesHeaderField, Proxy-Authorization]
-
A.
Authentication Header
Authentication Header is an IPsec protocol that provides connectionless integrity and data origin authentication for IP packets, optionally protecting against replay attacks.
-
B.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
C.
RFC 2617
RFC 2617 is an Internet standard that defined HTTP authentication mechanisms, including Basic and Digest Access Authentication, before being superseded by RFC 7235.
-
D.
RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
-
E.
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.
- 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: Proxy-Authorization Triple: [RFC 2617, definesHeaderField, Proxy-Authorization]
Generated description
Proxy-Authorization is an HTTP request header used to provide credentials for authenticating a client to a proxy server.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Proxy-Authorization Target entity description: Proxy-Authorization is an HTTP request header used to provide credentials for authenticating a client to a proxy server.
-
A.
Authentication Header
Authentication Header is an IPsec protocol that provides connectionless integrity and data origin authentication for IP packets, optionally protecting against replay attacks.
-
B.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
C.
RFC 2617
RFC 2617 is an Internet standard that defined HTTP authentication mechanisms, including Basic and Digest Access Authentication, before being superseded by RFC 7235.
-
D.
RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
-
E.
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.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc491a34d08190b0795079d192a03d |
completed | March 31, 2026, 10:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cecd3a3c5c8190940a61e7e7b3e887 |
completed | April 2, 2026, 8:10 p.m. |
| NEDg | Description generation | batch_69cece908adc8190b6ea8d971868cbf8 |
completed | April 2, 2026, 8:16 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cecf14eaa481908f8630872c21b3b3 |
completed | April 2, 2026, 8:18 p.m. |
Created at: March 30, 2026, 6:31 p.m.