Triple

T7934554
Position Surface form Disambiguated ID Type / Status
Subject Jira E184255 entity
Predicate supportsAuthentication P203 FINISHED
Object SAML E345752 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: SAML | Statement: [Jira, supportsAuthentication, SAML]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SAML
Context triple: [Jira, supportsAuthentication, SAML]
  • A. SAML chosen
    SAML (Security Assertion Markup Language) is an XML-based open standard for exchanging authentication and authorization data between identity providers and service providers, commonly used for single sign-on (SSO) in web applications.
  • B. SSO
    SSO is the standard abbreviation for Ship Security Officer, the designated person responsible for a vessel’s security under international maritime regulations.
  • C. OpenID Connect
    OpenID Connect is an identity layer built on top of OAuth 2.0 that enables secure user authentication and single sign-on across applications.
  • D. Oracle Identity Federation
    Oracle Identity Federation is an enterprise software solution from Oracle that enables secure single sign-on and identity federation across organizational and cloud boundaries.
  • E. SecurID
    SecurID is a widely used two-factor authentication system that provides time-based one-time passwords via hardware or software tokens to enhance secure access to systems and data.
  • 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_69ca8290c21c8190906a5ca6fe2b03c4 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3aeb132c8190bea4906aaf51b869 completed March 31, 2026, 3:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5c0791e48190af18299c22f6a804 completed March 31, 2026, 5:30 a.m.
Created at: March 30, 2026, 5:08 p.m.