Triple

T4555261
Position Surface form Disambiguated ID Type / Status
Subject Joomla! E120463 entity
Predicate supportsRESTAPIsViaExtensions P48896 FINISHED
Object yes 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: yes | Statement: [Joomla!, supportsRESTAPIsViaExtensions, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsRESTAPIsViaExtensions
Context triple: [Joomla!, supportsRESTAPIsViaExtensions, yes]
  • A. hasAPIs
    Indicates that one entity provides or exposes application programming interfaces (APIs) that can be used or accessed by another entity.
  • B. supportsExtensionModel chosen
    Indicates that one entity provides compatibility or functionality for using a specified extension model associated with another entity.
  • C. supportsOperationsIn
    Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
  • D. supportsThirdPartyApplications
    Indicates that an entity is capable of working with, integrating, or allowing the use of software applications developed by external third parties.
  • E. supportedAs
    Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another 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_69bd4636f1648190a701445c2fcd9c17 completed March 20, 2026, 1:05 p.m.
NER Named-entity recognition batch_69bd5813af948190b10b02dadf6496bf completed March 20, 2026, 2:22 p.m.
PD Predicate disambiguation batch_69bd5223423c81908317351b58cff5f5 completed March 20, 2026, 1:56 p.m.
Created at: March 20, 2026, 1:09 p.m.