Triple

T1936423
Position Surface form Disambiguated ID Type / Status
Subject Liquid Retina XDR E41452 entity
Predicate contrastCapability P33709 FINISHED
Object very high contrast 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: very high contrast | Statement: [Liquid Retina XDR, contrastCapability, very high contrast]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: contrastCapability
Context triple: [Liquid Retina XDR, contrastCapability, very high contrast]
  • A. consideredCapability
    Indicates that something is regarded or evaluated as a potential capability of an entity.
  • B. comparisonRequirement
    Indicates that one entity must be evaluated or measured in relation to another according to a specified standard or criterion.
  • C. primaryCapability
    Indicates that one entity serves as the main or most important functional ability, role, or competence of another entity.
  • D. usedCapability
    Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
  • E. featureLevelComparedTo
    Indicates a comparative relationship between entities based on their feature level, specifying how one entity’s feature level ranks relative to another’s.
  • 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_69a88649b24c819080047f26b6db2ded completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb2c5f6e481909b2d95861e2098f9 completed March 7, 2026, 5:08 a.m.
PD Predicate disambiguation batch_69abaff07cf88190b4883c5f17f90abd completed March 7, 2026, 4:56 a.m.
PDg Predicate description generation batch_69abb25ef0ec8190b907963e9db0fe04 completed March 7, 2026, 5:06 a.m.
Created at: March 4, 2026, 7:35 p.m.