Triple

T7977045
Position Surface form Disambiguated ID Type / Status
Subject RFC 6750 E185472 entity
Predicate protocolFramework P1992 FINISHED
Object OAuth 2.0 Authorization Framework E35337 NE FINISHED

How this triple was built (3 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: OAuth 2.0 Authorization Framework | Statement: [RFC 6750, protocolFramework, OAuth 2.0 Authorization Framework]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: OAuth 2.0 Authorization Framework
Context triple: [RFC 6750, protocolFramework, OAuth 2.0 Authorization Framework]
  • A. OAuth 2.0 chosen
    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.
  • 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. 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.
  • D. OAuth Working Group
    The OAuth Working Group is an IETF body responsible for developing and maintaining the OAuth protocol standards for secure authorization on the web.
  • E. OpenID Connect
    OpenID Connect is an identity layer built on top of OAuth 2.0 that enables secure user authentication and single sign-on across applications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: protocolFramework
Context triple: [RFC 6750, protocolFramework, OAuth 2.0 Authorization Framework]
  • A. protocolFunction
    Indicates that one entity serves as a function, role, or operation defined within the rules or structure of a particular protocol for another entity.
  • B. protocol chosen
    Indicates that one entity defines or follows a specific set of rules or procedures governing how it interacts or communicates with another entity.
  • C. protocolLayer
    Indicates a relationship where a communication protocol operates at, or is associated with, a specific layer in a protocol stack or network architecture.
  • D. protocols
    Indicates that one entity defines, uses, or adheres to a specified set of rules or procedures governing how it interacts or communicates with another entity.
  • E. protocolName
    Indicates the specific communication or interaction protocol used or associated with an entity or connection.
  • F. None of above.

Provenance (4 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_69cc5677968881908835169157244962 completed March 31, 2026, 11:19 p.m.
PD Predicate disambiguation batch_69cb047a8e4c81909b79e0f0bf56440c completed March 30, 2026, 11:17 p.m.
Created at: March 30, 2026, 5:14 p.m.