Triple
T1634860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OAuth 2.0 |
E35337
|
entity |
| Predicate | standardizedIn |
P7508
|
FINISHED |
| Object |
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.
|
E185472
|
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 6750 | Statement: [OAuth 2.0, standardizedIn, RFC 6750]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6750 Context triple: [OAuth 2.0, standardizedIn, RFC 6750]
-
A.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
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 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 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
E.
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.
- 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 6750 Triple: [OAuth 2.0, standardizedIn, RFC 6750]
Generated description
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 6750 Target entity description: RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
-
A.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
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 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 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
E.
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.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90a1679408190a9faa7b22c388c4b |
completed | March 5, 2026, 4:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad6099979481908e2c506323d546dd |
completed | March 8, 2026, 11:42 a.m. |
| NEDg | Description generation | batch_69ad6111fcc8819086923966b485c592 |
completed | March 8, 2026, 11:44 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ad619f842c8190936b659b30d6aa10 |
completed | March 8, 2026, 11:46 a.m. |
Created at: March 4, 2026, 7:28 p.m.