Triple

T2944880
Position Surface form Disambiguated ID Type / Status
Subject Pixel 4a E79475 entity
Predicate wirelessChargingSupport P17641 FINISHED
Object no 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: no | Statement: [Pixel 4a, wirelessChargingSupport, no]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wirelessChargingSupport
Context triple: [Pixel 4a, wirelessChargingSupport, no]
  • A. supportsWirelessCharging chosen
    Indicates that one entity provides the capability for another entity to be charged without a physical wired connection, typically via inductive or similar wireless power transfer methods.
  • B. wirelessChargingStandard
    Indicates that one entity specifies or supports the particular wireless charging protocol or standard used by another entity.
  • C. supportsPowerDelivery
    Indicates that one entity is capable of providing electrical power to another entity through a compatible interface or connection.
  • D. wirelessSupportIntroduced
    Indicates that support for wireless functionality was added or became available for the first time.
  • E. fastChargingCapability
    Indicates that an entity has the ability to charge at a higher-than-standard power rate, significantly reducing the time needed to reach a usable or full charge.
  • 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_69ad8b1089588190b74d9e2505e45762 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad98b2752481908ec6f9a9cc24c0a7 completed March 8, 2026, 3:41 p.m.
PD Predicate disambiguation batch_69ad96088fb481909976b436c2b729d9 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 2:56 p.m.