Triple
T2555006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azure Active Directory |
E56711
|
entity |
| Predicate | supportsFeature |
P203
|
FINISHED |
| Object | OpenID Connect |
E184249
|
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: OpenID Connect | Statement: [Azure Active Directory, supportsFeature, OpenID Connect]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OpenID Connect Context triple: [Azure Active Directory, supportsFeature, OpenID Connect]
-
A.
OpenID Connect
chosen
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.
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.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
D.
SSO
SSO is the standard abbreviation for Ship Security Officer, the designated person responsible for a vessel’s security under international maritime regulations.
-
E.
JSON Web Tokens (JWT)
JSON Web Tokens (JWT) are a compact, URL-safe standard for securely transmitting digitally signed claims between parties, commonly used for stateless authentication and authorization in web applications.
- 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_69abd30d20e081908587c76064573150 |
completed | March 7, 2026, 7:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af5d1ad6b4819097f1d18a12aa2b89 |
completed | March 9, 2026, 11:51 p.m. |
Created at: March 6, 2026, 9:48 p.m.