Triple

T38635971
Position Surface form Disambiguated ID Type / Status
Subject Microsoft Graph JavaScript SDK E937572 entity
Predicate supportsAuthFlow 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 Graph JavaScript SDK, supportsAuthFlow, OAuth 2.0]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsAuthFlow
Context triple: [Microsoft Graph JavaScript SDK, supportsAuthFlow, OAuth 2.0]
  • A. supportsSignInMethod chosen
    Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
  • B. supportsIdentity
    Indicates that one entity upholds, validates, or reinforces the identity, self-concept, or role of another entity.
  • C. supportsFlowOf
    Indicates that one entity facilitates, enables, or maintains the movement or progression of another entity (such as a substance, resource, or process).
  • D. authenticationRequired
    Indicates that access to a resource or operation is restricted and can only be performed by entities that have successfully authenticated.
  • E. authenticationProvidedBy
    Indicates that the authentication or verification of identity for an entity is carried out or supplied by another specified entity.
  • 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_69f76ed5ca3c81909288f61fbf37b359 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a037c9141dc819098d7fcc36e69882c completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a2026248190b894436a578d79ac completed May 12, 2026, 7:06 p.m.
Created at: May 3, 2026, 4:32 p.m.