Triple

T921026
Position Surface form Disambiguated ID Type / Status
Subject WordPress E19882 entity
Predicate supportsPluginArchitecture P203 FINISHED
Object true 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: true | Statement: [WordPress, supportsPluginArchitecture, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsPluginArchitecture
Context triple: [WordPress, supportsPluginArchitecture, true]
  • A. supportedParadigm
    Indicates that one entity (such as a tool, language, or system) provides functionality or features that enable or are compatible with a particular paradigm or methodological approach.
  • B. supportsImplementationOf
    Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
  • C. supportsFeature chosen
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • D. supportsStructure
    Indicates that one entity bears or provides physical support to another entity, helping to hold it up or maintain its structural stability.
  • E. supportsProjectType
    Indicates that one entity is capable of handling, accommodating, or being compatible with a specified type of project.
  • 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_69a493a099788190a696d9d8408cbaf4 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b3120dbc81908362158fe3ffa889 completed March 1, 2026, 9:43 p.m.
PD Predicate disambiguation batch_69a4b295b02481908e5f53bfcb83cc94 completed March 1, 2026, 9:41 p.m.
Created at: March 1, 2026, 7:40 p.m.