Triple
T7977032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6750 |
E185472
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | The OAuth 2.0 Authorization Framework: Bearer Token Usage |
E185472
|
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: The OAuth 2.0 Authorization Framework: Bearer Token Usage | Statement: [RFC 6750, title, The OAuth 2.0 Authorization Framework: Bearer Token Usage]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: The OAuth 2.0 Authorization Framework: Bearer Token Usage Context triple: [RFC 6750, title, The OAuth 2.0 Authorization Framework: Bearer Token Usage]
-
A.
RFC 6750
chosen
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
-
B.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
C.
OAuth 2.0
OAuth 2.0 is an industry-standard authorization framework that enables applications to obtain limited access to user resources on HTTP services without exposing user credentials.
-
D.
JSON Web Tokens (JWT)
JSON Web Tokens (JWT) are a compact, URL-safe standard for securely transmitting digitally signed claims between parties, commonly used for stateless authentication and authorization in web applications.
-
E.
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.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bf716508190b4245bd5d89ae8c4 |
completed | March 31, 2026, 3:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbe0cc09a081909cb92cd4864ef50d |
completed | March 31, 2026, 2:57 p.m. |
Created at: March 30, 2026, 5:14 p.m.