Triple

T8672343
Position Surface form Disambiguated ID Type / Status
Subject HTTP authentication framework E205826 entity
Predicate allowsExtension P11253 FINISHED
Object new authentication schemes 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: new authentication schemes | Statement: [HTTP authentication framework, allowsExtension, new authentication schemes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allowsExtension
Context triple: [HTTP authentication framework, allowsExtension, new authentication schemes]
  • A. supportsExtensionsFrom
    Indicates that one entity is capable of recognizing, loading, or interoperating with extensions originating from another entity.
  • B. hasExtensionBy
    Indicates that one entity is extended, augmented, or further developed by another entity.
  • C. supportedExpansionOf
    Indicates that one entity actively aided, endorsed, or facilitated the growth, extension, or enlargement of another entity or domain.
  • D. extensionMechanism chosen
    Indicates that one entity provides a way to extend, customize, or add new functionality or components to another entity.
  • E. mayExtendTo
    Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
  • 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_69ca83529a9c8190b5c075b4f14636ed completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc491a34d08190b0795079d192a03d completed March 31, 2026, 10:22 p.m.
PD Predicate disambiguation batch_69cc4564e018819081036722f3e42a71 completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:31 p.m.