Triple

T277409
Position Surface form Disambiguated ID Type / Status
Subject SAS E5277 entity
Predicate supportsInterface P203 FINISHED
Object graphical user interface 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: graphical user interface | Statement: [SAS, supportsInterface, graphical user interface]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsInterface
Context triple: [SAS, supportsInterface, graphical user interface]
  • A. commonlyImplementedBy
    Indicates that the referenced item (e.g., a standard, interface, or pattern) is frequently realized or put into practice by the associated implementing entities.
  • B. supportsFeature chosen
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • C. hasSupported
    Indicates that one entity has provided assistance, endorsement, or backing to another entity, either materially, emotionally, or through advocacy.
  • D. implementedUnder
    Indicates that an action, policy, or process is carried out within the scope, authority, or framework defined by a particular higher-level plan, rule, or governing entity.
  • E. isBaseFor
    Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
  • 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_69a257e6c8788190987dfe705ca2912a completed Feb. 28, 2026, 2:50 a.m.
NER Named-entity recognition batch_69a25ded68c88190b1fc595ce329aeb9 completed Feb. 28, 2026, 3:15 a.m.
PD Predicate disambiguation batch_69a25b7480e881909399beccfc7ffb81 completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 2:59 a.m.