Triple
T20004172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBCharacteristic |
E494407
|
entity |
| Predicate | hasPropertyFlag |
P138321
|
FINISHED |
| Object | CBCharacteristicPropertyNotify |
—
|
NE NERFINISHED |
How this triple was built (3 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: CBCharacteristicPropertyNotify | Statement: [CBCharacteristic, hasPropertyFlag, CBCharacteristicPropertyNotify]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CBCharacteristicPropertyNotify Context triple: [CBCharacteristic, hasPropertyFlag, CBCharacteristicPropertyNotify]
-
A.
CBCharacteristic
CBCharacteristic is a CoreBluetooth class representing a specific piece of data (a characteristic) on a remote Bluetooth Low Energy peripheral’s service, including its value and associated properties.
-
B.
HMCharacteristic
HMCharacteristic is a HomeKit framework class in Apple’s HomeKit API that represents an individual, configurable property or attribute of a smart home accessory, such as a light’s brightness or a thermostat’s temperature.
-
C.
HMCharacteristicEvent
HMCharacteristicEvent is a HomeKit framework class that represents an event triggered by changes to a specific characteristic of a HomeKit accessory, typically used in defining home automation rules.
-
D.
CBPeripheralManager
CBPeripheralManager is an iOS CoreBluetooth class that lets an app act as a Bluetooth Low Energy peripheral, managing advertising and the publication of services and characteristics.
-
E.
NSNotification
NSNotification is an Objective-C class that encapsulates information about an event, including its name and optional associated data, for use in the Cocoa notification system.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: CBCharacteristicPropertyNotify Target entity description: CBCharacteristicPropertyNotify is a Core Bluetooth characteristic property that allows a peripheral to automatically send notifications to a connected central when the characteristic’s value changes.
-
A.
CBCharacteristic
CBCharacteristic is a CoreBluetooth class representing a specific piece of data (a characteristic) on a remote Bluetooth Low Energy peripheral’s service, including its value and associated properties.
-
B.
HMCharacteristic
HMCharacteristic is a HomeKit framework class in Apple’s HomeKit API that represents an individual, configurable property or attribute of a smart home accessory, such as a light’s brightness or a thermostat’s temperature.
-
C.
HMCharacteristicEvent
HMCharacteristicEvent is a HomeKit framework class that represents an event triggered by changes to a specific characteristic of a HomeKit accessory, typically used in defining home automation rules.
-
D.
CBPeripheralManager
CBPeripheralManager is an iOS CoreBluetooth class that lets an app act as a Bluetooth Low Energy peripheral, managing advertising and the publication of services and characteristics.
-
E.
NSNotification
NSNotification is an Objective-C class that encapsulates information about an event, including its name and optional associated data, for use in the Cocoa notification system.
- F. None of above. chosen
Provenance (2 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a3ad148190918f9dce755fe470 |
completed | April 20, 2026, 5:25 p.m. |
Created at: April 11, 2026, 3:33 p.m.