Triple
T2555457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft account |
E56720
|
entity |
| Predicate | authenticationProtocol |
P35861
|
FINISHED |
| Object | OAuth 2.0 |
E35337
|
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: OAuth 2.0 | Statement: [Microsoft account, authenticationProtocol, OAuth 2.0]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OAuth 2.0 Context triple: [Microsoft account, authenticationProtocol, OAuth 2.0]
-
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.
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.
-
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.
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.
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.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd30eec988190810346bb8b6cb489 |
completed | March 7, 2026, 7:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af655c8d7c8190bef109b10d04464f |
completed | March 10, 2026, 12:27 a.m. |
Created at: March 6, 2026, 9:48 p.m.