Triple

T29389652
Position Surface form Disambiguated ID Type / Status
Subject android.print.PrintAttributes.Resolution E745340 entity
Predicate labelUsage P89999 FINISHED
Object user-visible description of resolution 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: user-visible description of resolution | Statement: [android.print.PrintAttributes.Resolution, labelUsage, user-visible description of resolution]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: labelUsage
Context triple: [android.print.PrintAttributes.Resolution, labelUsage, user-visible description of resolution]
  • A. usedLabel
    Indicates that one entity has applied, assigned, or referenced a particular label to another entity or resource.
  • B. designationUsedFor
    Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
  • C. designationUse chosen
    Indicates how a particular designation or title is intended to be used or applied in relation to an entity.
  • D. labelIndication
    Indicates that a label or designation is assigned to an entity to specify its indication, purpose, or intended use.
  • E. classificationUsedBy
    Indicates that a particular classification system or scheme is employed or applied by a given 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_69f0a79dfabc81908755382ee47791e2 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f674e06c9481909ed0ea736408f0d7 completed May 2, 2026, 10:04 p.m.
PD Predicate disambiguation batch_69f673c4abec8190bc2379e66f4af0a9 completed May 2, 2026, 9:59 p.m.
Created at: April 28, 2026, 2:41 p.m.