Triple

T7935742
Position Surface form Disambiguated ID Type / Status
Subject Monochrome Display Adapter E184284 entity
Predicate graphicsSupport P28918 FINISHED
Object no bitmapped graphics support 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: no bitmapped graphics support | Statement: [Monochrome Display Adapter, graphicsSupport, no bitmapped graphics support]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: graphicsSupport
Context triple: [Monochrome Display Adapter, graphicsSupport, no bitmapped graphics support]
  • A. graphicsCapabilities
    Indicates the level or type of graphical processing features or performance that an entity supports or provides.
  • B. graphicsAPI
    Indicates a relationship where one entity uses, supports, or is implemented with a particular graphics application programming interface (graphicsAPI).
  • C. graphicsAdapter
    Indicates a relationship where a device or system is associated with, uses, or is equipped with a particular graphics adapter (graphics processing hardware).
  • D. graphicsType chosen
    Indicates the type or category of graphics associated with or used by an entity.
  • E. graphics
    Indicates a relationship where one entity is responsible for creating, providing, or handling visual representations or graphical content for another entity or context.
  • 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_69ca8290c21c8190906a5ca6fe2b03c4 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3aec394081909a9569c02ac372af completed March 31, 2026, 3:09 a.m.
PD Predicate disambiguation batch_69cae9335f288190ba96781fd6576a2b completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 5:08 p.m.