Triple

T1892185
Position Surface form Disambiguated ID Type / Status
Subject FaceTime HD camera E41896 entity
Predicate typicalResolution P33105 FINISHED
Object 720p 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: 720p | Statement: [FaceTime HD camera, typicalResolution, 720p]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalResolution
Context triple: [FaceTime HD camera, typicalResolution, 720p]
  • A. displayResolution
    Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
  • B. telephotoCameraResolution
    Indicates the image resolution capability of a device’s telephoto camera in a given context.
  • C. typicalWidth
    Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
  • D. typicalHeight
    Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
  • E. mediaAspect
    Indicates the specific aspect ratio or dimensional proportion of a media item in relation to its width and height.
  • 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_69a8864b6de0819098d089f6a1b910a7 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb145f96c8190a71bb9e442892e68 completed March 7, 2026, 5:01 a.m.
PD Predicate disambiguation batch_69abafe61bc48190ac9ead027df930e1 completed March 7, 2026, 4:56 a.m.
PDg Predicate description generation batch_69abb11bfd2c8190a805372589f73238 completed March 7, 2026, 5:01 a.m.
Created at: March 4, 2026, 7:34 p.m.