Triple

T8471534
Position Surface form Disambiguated ID Type / Status
Subject Control Panels (classic Mac OS) E200290 entity
Predicate customizability P33710 FINISHED
Object third-party developers could add custom control panels 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: third-party developers could add custom control panels | Statement: [Control Panels (classic Mac OS), customizability, third-party developers could add custom control panels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: customizability
Context triple: [Control Panels (classic Mac OS), customizability, third-party developers could add custom control panels]
  • A. customizableBy chosen
    Indicates that one entity can be modified, configured, or tailored in some way by another entity.
  • B. custom
    Indicates that something is specially created, configured, or tailored for a particular purpose, context, or user rather than being standard or generic.
  • C. reconfigurability
    Indicates the capability of something to be rearranged, adapted, or modified into different configurations or functional setups.
  • D. programmability
    Indicates that an entity can be configured, controlled, or modified through programming or code to change its behavior or functions.
  • E. tunable
    Indicates that the associated entity can be adjusted or configured to different settings or values, typically to optimize performance or behavior.
  • 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_69ca831a4f348190bfdd09250e86ae35 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe4f3a81881908f20514579945ffa completed March 31, 2026, 3:14 p.m.
PD Predicate disambiguation batch_69cbd10072cc819084be1ed9ac7ebe9d completed March 31, 2026, 1:49 p.m.
Created at: March 30, 2026, 6:11 p.m.