Triple

T27591069
Position Surface form Disambiguated ID Type / Status
Subject Pulp API E699789 entity
Predicate hasAuthentication P170971 FINISHED
Object token-based authentication 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: token-based authentication | Statement: [Pulp API, hasAuthentication, token-based authentication]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAuthentication
Context triple: [Pulp API, hasAuthentication, token-based authentication]
  • A. hasCredential
    Indicates that an entity possesses or has been granted a specific credential, qualification, or certification.
  • B. authenticationOptional
    Indicates that the authentication step is not required and may be skipped or bypassed for the associated action or relationship.
  • C. authenticationRequired
    Indicates that access to a resource or operation is restricted and can only be performed by entities that have successfully authenticated.
  • D. overseesAuthenticationOf
    Indicates that one entity is responsible for supervising, managing, or ensuring the proper execution of another entity’s authentication process.
  • E. hasSecurityPresence
    Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
  • F. None of above. chosen

Provenance (4 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_69ef6a4d71f081909a1235763206b691 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f6984bb55c8190862eb8796868d188 completed May 3, 2026, 12:35 a.m.
PD Predicate disambiguation batch_69f69661e6ec8190948251c7516a32ad completed May 3, 2026, 12:27 a.m.
PDg Predicate description generation batch_69f6978ec27c8190a488e1f9c2566d38 completed May 3, 2026, 12:32 a.m.
Created at: April 27, 2026, 2:05 p.m.