Triple
T19585457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty ID-FF |
E490095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | single sign-on specification |
C3606
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: single sign-on specification Context triple: [Liberty ID-FF, instanceOf, single sign-on specification]
-
A.
OAuth 2.0 specification
The OAuth 2.0 specification defines a framework for delegated authorization that enables applications to obtain limited access to user resources on an HTTP service without exposing user credentials.
-
B.
authentication standard
An authentication standard is a defined set of rules and protocols that specify how identities are verified and access is securely granted across systems and applications.
-
C.
interoperability specification suite
chosen
An interoperability specification suite is a coordinated set of technical standards, protocols, and guidelines designed to ensure that diverse systems, components, or organizations can reliably exchange and correctly interpret data and functionality.
-
D.
authorization framework
An authorization framework is a structured system of rules, components, and processes that determines and enforces what actions users or services are permitted to perform on protected resources.
-
E.
online authentication credential
An online authentication credential is a piece of digital information (such as a password, token, certificate, or biometric template) used to verify and grant a user's identity and access rights in an online system.
- F. None of above.
Provenance (1 batch)
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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:42 p.m.