Triple

T7933983
Position Surface form Disambiguated ID Type / Status
Subject RFC 6749 E184245 entity
Predicate workingGroup P9939 FINISHED
Object 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.
 E697199 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: OAuth Working Group | Statement: [RFC 6749, workingGroup, OAuth Working Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: OAuth Working Group
Context triple: [RFC 6749, workingGroup, OAuth Working Group]
  • A. HTTP Working Group
    The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
  • B. 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.
  • C. 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.
  • D. W3C Coordination Group
    The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
  • E. W3C Working Group
    A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
  • 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: OAuth Working Group
Triple: [RFC 6749, workingGroup, OAuth Working Group]
Generated description
The OAuth Working Group is an IETF body responsible for developing and maintaining the OAuth protocol standards for secure authorization on the web.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: OAuth Working Group
Target entity description: The OAuth Working Group is an IETF body responsible for developing and maintaining the OAuth protocol standards for secure authorization on the web.
  • A. HTTP Working Group
    The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
  • B. 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.
  • C. 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.
  • D. W3C Coordination Group
    The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
  • E. W3C Working Group
    A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
  • 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_69cb3aeb132c8190bea4906aaf51b869 completed March 31, 2026, 3:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5c041e588190bfbf251ed88d5bcd completed March 31, 2026, 5:30 a.m.
NEDg Description generation batch_69cb5f22f89c8190a98208bf096a2427 completed March 31, 2026, 5:44 a.m.
NED2 Entity disambiguation (via description) batch_69cb76d2dff8819085ad9e10baad1537 completed March 31, 2026, 7:25 a.m.
Created at: March 30, 2026, 5:08 p.m.