Triple
T7933998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OAuth 1.0 |
E184246
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | authorization protocol |
C11228
|
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: authorization protocol Context triple: [OAuth 1.0, instanceOf, authorization protocol]
-
A.
authorization framework
chosen
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.
-
B.
authentication credential
An authentication credential is a piece of information or object (such as a password, token, certificate, or biometric template) used to verify and prove a user's identity to a system or service.
-
C.
authentication message
An authentication message is a structured communication containing credentials or security tokens used to verify the identity of a user, device, or system before granting access to protected resources.
-
D.
authentication feature
An authentication feature is a system component that verifies and confirms a user's identity before granting access to protected resources or actions.
-
E.
authentication service
An authentication service is a system component that verifies and manages user or system identities to control access to protected resources.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:08 p.m.