Triple
T12325570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTI |
E293820
|
entity |
| Predicate | basedOn |
P98
|
FINISHED |
| Object | OAuth 1.0 (early versions) |
E184246
|
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 1.0 (early versions) | Statement: [LTI, basedOn, OAuth 1.0 (early versions)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OAuth 1.0 (early versions) Context triple: [LTI, basedOn, OAuth 1.0 (early versions)]
-
A.
OAuth 1.0
chosen
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.
-
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.
OAuth
OAuth is an open standard authorization framework that enables secure, delegated access to protected resources without sharing user credentials.
-
D.
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.
-
E.
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.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f4e7e588190b37e2413bc649198 |
completed | April 10, 2026, 6:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e8d27288190bdf32acd600141db |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:53 p.m.