Triple

T35076652
Position Surface form Disambiguated ID Type / Status
Subject MIUI E1012324 entity
Predicate updateDeliveryModel P113797 FINISHED
Object over-the-air updates 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: over-the-air updates | Statement: [MIUI, updateDeliveryModel, over-the-air updates]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: updateDeliveryModel
Context triple: [MIUI, updateDeliveryModel, over-the-air updates]
  • A. updateDelivery
    Indicates that an existing delivery’s details or status are modified or refreshed, typically to reflect new information or changes in its execution.
  • B. deliveryModelOf chosen
    Indicates that one entity functions as the delivery model or mechanism through which another entity (such as a service, product, or program) is provided or made available.
  • C. deliveryAid
    Indicates that one entity provides assistance, resources, or support to facilitate the delivery or distribution of something to another entity.
  • D. formerlyDeliveryMode
    Indicates that an entity previously used a particular delivery mode but no longer does so.
  • E. deliveryMode
    Indicates the method or channel through which something (such as a product, service, or information) is delivered or provided.
  • 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_69f76dd32c008190853aef6028f60208 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7865d9dcc81909deaf635acd9ef56 completed May 3, 2026, 5:31 p.m.
PD Predicate disambiguation batch_69f7841812f081909d878955d114088e completed May 3, 2026, 5:21 p.m.
Created at: May 3, 2026, 4:01 p.m.