Triple

T27738093
Position Surface form Disambiguated ID Type / Status
Subject MatFormField E697576 entity
Predicate supportsAppearance P201420 FINISHED
Object legacy 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: legacy | Statement: [MatFormField, supportsAppearance, legacy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsAppearance
Context triple: [MatFormField, supportsAppearance, legacy]
  • A. supportsView
    Indicates that one entity provides the capability to display, render, or present another entity in a particular view or format.
  • B. supportsAspect
    Indicates that one entity provides backing, justification, or reinforcement for a particular aspect, feature, or component of another entity.
  • C. supportsAlignment
    Indicates that one entity is compatible with and can properly function or operate in conjunction with a specified alignment, configuration, or standard.
  • D. supportsPersonalization
    Indicates that one entity enables or provides functionality for tailoring content, behavior, or experience to the preferences or characteristics of another entity.
  • E. supportedView
    Indicates that one entity provides or enables a particular view, perspective, or representation that is available for use by another entity.
  • 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_69ef590c3e288190ad54d2465af8ca4e completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69fff4530f908190afe9387f732c2b7e completed May 10, 2026, 2:58 a.m.
PD Predicate disambiguation batch_69fff3c01a64819091196875b0c88607 completed May 10, 2026, 2:56 a.m.
PDg Predicate description generation batch_69fff4525ce48190b1d760539e68aadc completed May 10, 2026, 2:58 a.m.
Created at: April 27, 2026, 3:13 p.m.