Triple

T29456588
Position Surface form Disambiguated ID Type / Status
Subject HAM-8 display mode E747117 entity
Predicate alsoSupportedResolution P74451 FINISHED
Object 640×512 interlaced PAL 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: 640×512 interlaced PAL | Statement: [HAM-8 display mode, alsoSupportedResolution, 640×512 interlaced PAL]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: alsoSupportedResolution
Context triple: [HAM-8 display mode, alsoSupportedResolution, 640×512 interlaced PAL]
  • A. supportsDisplayResolution chosen
    Indicates that one entity is capable of operating with, rendering, or otherwise accommodating the specified display resolution of another entity.
  • B. typicalResolution
    Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
  • C. displayResolution
    Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
  • D. alsoSupports
    Indicates that an entity, in addition to its primary or previously stated function, provides support for another entity, feature, or activity.
  • E. supportedIn
    Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
  • 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_69f0bd4125f88190b56104591351619c completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66b6cf8fc81909cd68959b362dde0 completed May 2, 2026, 9:23 p.m.
PD Predicate disambiguation batch_69f66339175c819080bd70f0ff7057b1 completed May 2, 2026, 8:48 p.m.
Created at: April 28, 2026, 3:46 p.m.