Triple

T2654433
Position Surface form Disambiguated ID Type / Status
Subject Apple A14 Bionic E53974 entity
Predicate supportsOnDeviceEncryption P39134 FINISHED
Object true 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: true | Statement: [Apple A14 Bionic, supportsOnDeviceEncryption, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsOnDeviceEncryption
Context triple: [Apple A14 Bionic, supportsOnDeviceEncryption, true]
  • A. requiresEncryption
    Indicates that one entity must use encryption when communicating with, storing data for, or otherwise interacting with another entity.
  • B. usesEncryptionAlgorithm
    Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
  • C. integratedSecureEnclave chosen
    Indicates that a system or component includes a built-in secure enclave that isolates and protects sensitive operations or data from the rest of the environment.
  • D. supportsParallelEncryption
    Indicates that the subject is capable of performing encryption operations in parallel, rather than strictly sequentially.
  • E. requiresDevice
    Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
  • 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_69ab495e192081909c77b622e8e7e15a completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abda0ba2208190ad87763ecbef8c3c completed March 7, 2026, 7:55 a.m.
PD Predicate disambiguation batch_69abd815d06481909535c02b0aba8553 completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:53 p.m.