Triple

T28616518
Position Surface form Disambiguated ID Type / Status
Subject ChooseFont E724284 entity
Predicate configurableViaFlag P74449 FINISHED
Object CF_SCREENFONTS 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: CF_SCREENFONTS | Statement: [ChooseFont, configurableViaFlag, CF_SCREENFONTS]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: configurableViaFlag
Context triple: [ChooseFont, configurableViaFlag, CF_SCREENFONTS]
  • A. definesFlag
    Indicates that one entity specifies or establishes a particular flag or boolean indicator used by another entity or process.
  • B. alternativeFlag
    Indicates that something is marked or designated as an alternative option or variant relative to a primary or default choice.
  • C. canBeReconfigured
    Indicates that one entity has the capability to be altered, adjusted, or rearranged into a different configuration, typically under certain conditions or using specific methods.
  • D. commandFlag
    Indicates that one entity issues a directive or control instruction (a command) that another entity is expected to recognize or act upon.
  • E. featureFlag chosen
    Indicates that a particular functionality or behavior is conditionally enabled or disabled for an entity based on a configurable flag.
  • 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_69f01d816d7c8190a1fe27e3434041dc completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f6b903538481909cffcb6cc1cc0e70 completed May 3, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69f6b626120c819097c9ad04487570d7 completed May 3, 2026, 2:42 a.m.
Created at: April 28, 2026, 4:32 a.m.