Triple
T27612914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Search API |
E700369
|
entity |
| Predicate | supportsAuthenticationFlow |
P40818
|
FINISHED |
| Object | OAuth 2.0 |
—
|
LITERAL 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 Search API, supportsAuthenticationFlow, OAuth 2.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAuthenticationFlow Context triple: [Microsoft Search API, supportsAuthenticationFlow, OAuth 2.0]
-
A.
hasAuthentication
Indicates that an entity is associated with or requires a specific method or mechanism of authentication.
-
B.
overseesAuthenticationOf
Indicates that one entity is responsible for supervising, managing, or ensuring the proper execution of another entity’s authentication process.
-
C.
authenticationStandard
Indicates that one entity defines, specifies, or adheres to a particular method, protocol, or set of rules for verifying the identity of another entity.
-
D.
authenticationOptional
Indicates that the authentication step is not required and may be skipped or bypassed for the associated action or relationship.
-
E.
supportsSignInMethod
chosen
Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
- F. None of above.
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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: April 27, 2026, 2:11 p.m.