Triple

T7934245
Position Surface form Disambiguated ID Type / Status
Subject OpenID Connect E184249 entity
Predicate replaces P101 FINISHED
Object OpenID 2.0
OpenID 2.0 is an earlier decentralized authentication protocol that allowed users to sign into multiple websites using a single identity URL, later superseded by OpenID Connect.
E700379 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: OpenID 2.0 | Statement: [OpenID Connect, replaces, OpenID 2.0]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: OpenID 2.0
Context triple: [OpenID Connect, replaces, OpenID 2.0]
  • A. 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.
  • B. SAML
    SAML (Security Assertion Markup Language) is an XML-based open standard for exchanging authentication and authorization data between identity providers and service providers, commonly used for single sign-on (SSO) in web applications.
  • 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. RFC 6749
    RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
  • E. OAuth 1.0
    OAuth 1.0 is an older open standard authorization protocol that enabled secure delegated access to web resources without sharing user credentials, and has since been superseded by OAuth 2.0.
  • 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: OpenID 2.0
Triple: [OpenID Connect, replaces, OpenID 2.0]
Generated description
OpenID 2.0 is an earlier decentralized authentication protocol that allowed users to sign into multiple websites using a single identity URL, later superseded by OpenID Connect.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: OpenID 2.0
Target entity description: OpenID 2.0 is an earlier decentralized authentication protocol that allowed users to sign into multiple websites using a single identity URL, later superseded by OpenID Connect.
  • A. 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.
  • B. SAML
    SAML (Security Assertion Markup Language) is an XML-based open standard for exchanging authentication and authorization data between identity providers and service providers, commonly used for single sign-on (SSO) in web applications.
  • 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. 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.
  • E. RFC 6749
    RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
  • 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_69cb5c0791e48190af18299c22f6a804 completed March 31, 2026, 5:30 a.m.
NEDg Description generation batch_69cb7633c5a0819089deb6e89d9acb8e completed March 31, 2026, 7:22 a.m.
NED2 Entity disambiguation (via description) batch_69cbb84dc86c8190893d67ce07c51aa0 completed March 31, 2026, 12:04 p.m.
Created at: March 30, 2026, 5:08 p.m.